Quote Originally Posted by Naiw View Post
Exactly this. And when it comes to Square Enix in general they have a long history of similar behaviors- pushing issues under the rug and if and only if they're fixing them it's because they see a chance to grab even more of your money. This expansion has been paid by every player who currently can not play and even those who have not bought the expansion is unable to play the game, not everyone are unemployeed and have their parents serve them with food and stuff- some of us are only able to play maybe an hour or two at of course peak hours.
This. Let's not talk about the glamour dresser not being available as a housing furniture lol.

Quote Originally Posted by Naiw View Post
I don't understand people at all that defends this or claims "they warned us", yeah so what? what if HBO warned that all subscribers will be unable to watch their service because everyone wants to see the latest WB movie they got, while the FFXIV user agreement explicitly states that you are not allowed to take legal action against SE, it's probably not unlikely that would succeed in court. This is a paid service and that's when obligations come into play- there are clauses for intermittent loss of service but as this is far from intermittent and it has been predicted by pretty much everyone, non the less they kept selling preorders knowingly that just a handful of the players would be able to play, it's shady at best.
I agree completely with you. That is shady at best. In the era of cloud computing everywhere, SE should have been able to prevent, mitigate this issue at the very least. They did not. Despite encountering the same issues 3 years ago with ShB, 5 years ago with SB and 9 years ago with ARR (I dont know for HW, I wasn't here). I must add, they knew at each major patch they have issue. They had issue at 5.2, 5.4 with queues ranging from 600 to 1k at raid time. One disconnect within the roster meant 20min of wait fore him to fend off the queue to log back into the instance.
And this issue has been reported time and time again. SE does a poor job at saving your place in queue (it works for a few people, for most of the people it does not). SE does a poor job at not timing you out off of queue (why the hell does it need a full time connection with you again ? A 5min poll with a 15min timeout after a poll-failing and associating your login credentials with your queue ticket should be the absolute minimum).
On that issue, I have my theory. I believe if you have a two-factor authentication your credential changes each time you relog in queue due to re-entering the 6 digits hence making you loose your place in queue.
And finally, SE does a poor job at evolving their infrastructure to something that can scale... They should have been to handle the issue they are facing right now.