Concrete proof finally provided that the 2002 error has NOTHING is server side issue

[Arazehl]

I will one up you. I 2002 at 60 and in the ten seconds it took me to get back in que I moved to 1. It makes zero sense and most times I move to the end of the line.

Ah but got an even better one. The other day I was 1098 in queue and 20 seconds later I was loading into the game. Wonder what playing during the weekdays has in store for this week?

[Sora_Oathkeeper]

I hate when people use the word "proof" in this way. This doesn't prove anything, it does however strongly suggest in a perfect network environment that there is something going wrong on SE end when the reconnect happens. You can still get error 2002 at any other point other than the 15min increment if you lose packets or drop connection briefly which is what the OP mentioned multiple times throughout the comment section which you ignored entirely.

This feels like a typical media article misreporting research and spreading misinformation.

Tl:dr - error 2002 occurs if you lose packets at any point during login, AND it can occur server side when attempting to reconnect you every 15 minutes.

[Puremallace]

This feels like a typical media article misreporting research and spreading misinformation.

Tl:dr - error 2002 occurs if you lose packets at any point during login, AND it can occur server side when attempting to reconnect you every 15 minutes.

I summarized what the original poster said but I linked to the data to backup my claim. As I am unable to explain why their client works like this I cannot word it correctly. All I know is the claim from Square Enix that this 100% falls on the user responsibility is blatantly a misrepresentation of the actual facts.

This claim by Square Enix goes all the way back to 2014 and is an issue on their end. The only way to truly solve the issue appear to have VPN as close as possible to their servers to prevent any packet loss during the login process. I do not understand why Square Enix did not expect some very smart people to look at this error when they claim it is user error.

It has NOTHING to do with COVID as it an issue that goes back 7 years. It is how they choose to handle traffic to their servers and how this client is built.

[ZetsubouX]

Funny how I never get 2002'd, even while in a 6000+ queue, then.
Must be Her blessing.

[Chie_M]

I'm generally a pretty blatant white knight, but even I'm raising my eyebrows at their continued insistence that the 2002 error is packet loss when it's so obviously a server-side issue. Come on, Square.

[Seraphor]

I haven't had a 2002 error since the patch.

Same. Patched fixed it for Zodiark. This is a server by server issues, likely worse on the most populated servers

[Asmo86]

They knew this from the start I'm sure and were just trying to deflect blame as a form of damage control. It sucks and I just hope everyone gets a chance to play soon.

[Seraphor]

I summarized what the original poster said but I linked to the data to backup my claim. As I am unable to explain why their client works like this I cannot word it correctly. All I know is the claim from Square Enix that this 100% falls on the user responsibility is blatantly a misrepresentation of the actual facts.

This claim by Square Enix goes all the way back to 2014 and is an issue on their end. The only way to truly solve the issue appear to have VPN as close as possible to their servers to prevent any packet loss during the login process. I do not understand why Square Enix did not expect some very smart people to look at this error when they claim it is user error.

It has NOTHING to do with COVID as it an issue that goes back 7 years. It is how they choose to handle traffic to their servers and how this client is built.

If you can solve the issue with a vpn... doesn't that confirm it's an issue with packet loss on the user end?

[Chooty]

Funny how I never get 2002'd, even while in a 6000+ queue, then.
Must be Her blessing.

EU seems to have been fixed or at least gotten a lot better after their login server maintenance. I had multiple 2002 errors per day before maintenance, and haven't had a single one since.

[Tsukino]

Regardless of how the error occurs, it's not the real problem. The real problem is the client closing down completely when the error is encountered, rather than just attempting to automatically reconnect for you or kicking you back to the title screen and letting you hit Start again. If we didn't have to constantly babysit the thing and then scramble to re-enter our passwords, the error would be a minor annoyance. And the client being made the way it is, is obviously a problem on their end to fix without any "proof" required.