https://www.youtube.com/watch?v=C6U926lsM-w
When a company "blames" something as the cause of a problem when it isnt the cause of the problem, the problem doesnt get fixed. The company has to understand their problem in order to fix the problem, and players have providd plenty of data as to the causes of the problems and they should be able to take steps to remedy them. The easiest would be that for this disconnect errors simply add in a couple of checks to see if the player's client started responding. For example when it would generate the 2002 and close the client, instaed check to see if the connection is there and then continue on in queue. For the error 90002, simply put a check right before booting the player to see if the client is responding and if so, reconnec them immediately. I just got booted out at the end of a cutscene just to have the game tell me my character wasnt properly logged out and it was going to log me out before I could log back in... when it should just reconned me to exactly where I was.
Their client has some bad design choices that are becoming major issues with the queues where they were just stupid annoyances before
You're kidding right? FFXIV dev team isn't sexually harassing women or stealing breast milk. You're not being scammed, It's just an unfortunate event that's happening due to the worldwide chip shortage affecting multiple businesses.
That is exactly what it is a quick fix because their servers would crash due to the influx of people attempting to queue at the same time or waiting in the queue.
It's a tough situation, and I'm pretty sure their IT team is doing everything possible to keep the servers up because it can be extremely costly if the servers crashed and no one would be able to login.
Greetings fellow Eorzean,
We apologize for the inconvenience you have experienced with server congestion on Final Fantasy XIV. Due to the recent release of Endwalker, we are experiencing an extremely high surge in player base which may result in long queue times and possible connection based errors. We are aware of this inconvenience and have addressed it in the following Lodestone post:
https://na.finalfantasyxiv.com/lodes...9264ac9f24986f
We appreciate your patience and understanding regarding this matter and ask that you try again at a later time to see if the issue persists along with keeping an eye out on the Lodestone website when further updates will become available.
Thank you for visiting the Final Fantasy XIV Technical Support forums!
This "quick fix" makes no sense when you want to relieve a server from too many connections. It makes the things even worse because when you reestablish a connection then this costs slightly more ressources than keeping a connection alive. I have read an argument that this behavior could fix some home routers which shutdown a connection when there is almost no activity on a network port. This argument makes sense to me even i have never heard of it that routers do such things.
But this behavior of the game client should be configurable. I mean, you should be able to switch it off. And there should be a proper reconnect functionality. If the lobby server is full then the client should wait 10 seconds and then try again. And that multiple times.
Cheers
That document has a major flaw, as the poster of it is testing only his connection. Not the connection of others so it does not eliminate your own ISP as being the problem. Simply confirms the client issue which SE also confirmed themselves.
Only two people can confirm if your connection is the issue YOU AND SE!!! Not joe blow the internet bro
Pretty sure that if it was a problem with an individuals internet, there wouldn't be as many people reporting these DCing issues in the 9000X category right now. Needs to be looked at closer by the developers and fixed.