They knew this was coming and did nothing about it.

[Sanjoo]

All am hearing is blah blah Covid and blah blah Shortage of Semiconductors, these people that constantly quote this probably have no idea what a conductor is, they had a year to get more computers, a whole year, there is no global shortage of computers. They chose not to because they didn't want to pay higher prices, they are server desktops on every site, so please enough with this semiconductor bloomberg nonsense.

[lezard21]

The "indie company didn't expect huge player explosion" excuse really doesn't work.

Square Enix sold the expansion and charged the monthly fees. Square Enix had the sales number and should have realised that the number greatly exceeded their outdated servers' capacity. Those sales did not happen the morning before EW launch.

Saying a week earlier "oh btw, too many people might have bought the game so expect congestion, woops" after you've already purchased the expansion and paid your monthly fee is not a warning.

Square Enix should have refunded Endwalker and monthly fee to everyone along with a disclaimer stating that the amount of players intending to play the expansion was way beyond their outdated server capacity.

Then, and only then, if people still bought the expansion and faced the congestion would they have had no right to complain.

But that's not what happened at all.

Square took our money and now people are not getting access to the service they paid believing they would be able to.

So people have a right to complain and demand compensation.

[Momo_Kozuki]

The "indie company didn't expect huge player explosion" excuse really doesn't work.

Square Enix sold the expansion and charged the monthly fees. Square Enix had the sales number and should have realised that the number greatly exceeded their outdated servers' capacity. Those sales did not happen the morning before EW launch.

.

You forgot that free-trials and people who don't pay for EW yet also access the same servers of EW buyers. And they are still able to log in during EW Early Access, just without the access to EW's contents (MSQ, new regions and new classes).


Basically, it is the same number of pre-EW early access launch who continues do whatever pre-EW they can do, plus the early-access people who flock to shiny and new contents.

[Jadedsins]

You know this would not be a issue if they changed how the queue works. When you get a error, instead of kicking you out of the game. To auto requeue you back in. HOW IS THAT SO HARD?


And add a buffer for when you get DC in the game, for a short time to get back into the game so you don't get punished back in queue.



This is common sense. This is what most of us are upset about.

[Krotoan]

You know this would not be a issue if they changed how the queue works. When you get a error, instead of kicking you out of the game. To auto requeue you back in. HOW IS THAT SO HARD?


And add a buffer for when you get DC in the game, for a short time to get back into the game so you don't get punished back in queue.

Please explain, in detail, how to code this in then. Because you seem to know exactly how it works and exactly how to fix it. I'm sure the devs will be happy to implement the perfect solution you have come up with.

[DrFlesh]

Please explain, in detail, how to code this in then. Because you seem to know exactly how it works and exactly how to fix it. I'm sure the devs will be happy to implement the perfect solution you have come up with.

ask the bad boys that work at blizzard, maybe they can tell them how they did it 8 years ago on wow, overwatch and hots

You forgot that free-trials and people who don't pay for EW yet also access the same servers of EW buyers. And they are still able to log in during EW Early Access, just without the access to EW's contents (MSQ, new regions and new classes).


Basically, it is the same number of pre-EW early access launch who continues do whatever pre-EW they can do, plus the early-access people who flock to shiny and new contents.

free trials can't play when there is a queue

[Krotoan]

ask the bad boys that work at blizzard, maybe they can tell them how they did it 8 years ago on wow, overwatch and hots

The comparison tells me you have no idea either. It's like saying GW2s wardrobe system did it, why can't FFXIV? Because it's an entire other game and while possibly things are functionality similar it may be the difference between a glass window and a Hard Candy window. Superficially similar but the process to make each is oceans apart.

My point being it's easy to say "why don't you just fix it" but there are very likely GOOD reasons they haven't or are hesitant to. It's possible the reason is nobody will approve all the labor and cost to do so, but that's not a particularly bad one.

[Larirawiel]

ask the bad boys that work at blizzard, maybe they can tell them how they did it 8 years ago on wow, overwatch and hots

The servers in WoW do not work very well. They do not have huge queues (OK, WoW classic was a big exception with 20+k queues. ) but they are very laggy. You have ability lags on open world bosses, loot lag, lags when you buy from or sell something to a vendor etc.

Cheers

[DrFlesh]

The servers in WoW do not work very well. They do not have huge queues (OK, WoW classic was a big exception with 20+k queues. ) but they are very laggy. You have ability lags on open world bosses, loot lag, lags when you buy from or sell something to a vendor etc.

Cheers

so many strawman arguments on this forum lol i understand wow bad ffxiv good, but we are talking about the queue system and in wow is extremely robust while here is just crap

in world of satancraft when you get disconnected and there is a queue you can reconnect instantly because every player that was in the game has a 10 min grace period to reconnect, the same thing happens when you get dc while on queue, there is literally no excuse to no have this function when the "enemy team" implemented that almost 10 years ago

[LittleImp]

This was largely a QA failure; They lacked the foresight or capacity to test their lobby/queue system at scale, and this is the result.

Some people were snooping around with network diagnostic tools and concluded that the client periodically attempts to reestablish its existing connection with the lobby server; The servers are pretty taxed right now, so sometimes the server fails to respond in time or at all to this request. It seems that instead of continuously retrying to establish the connection in the event of a failure, it just throws the dreaded error instead and closes the client.