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

[ijuakos_xqwzts]

(from the linked Google document)
I have fiber internet and a direct ethernet connection to my computer, and I get it all the damn time despite having zero issues maintaining a connection to any other game or service.

Funny. Because I have a cable internet and my connection goes through an 8-port Gigabit switch, 24-port PoE Gigabit switch, a 40GB optical bridge to a 48-port Gigabit switch, to my security gateway, and finally to my modem. No issues what-so-ever, even in a 5000-ish size queue a couple nights ago. Another fun fact: I also took the family out to dinner that night and, by the time we got back and unwound, I only had 10-15 minutes before I was in.

However, it piques my interest and maybe I'll remote into one of my switches to sniff the traffic next time I have to deal with the queue. If this is what is going on, it should be easily reproducible.

[Puremallace]

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

So the core issue is the single attempt before tanking the client. Requiring a complete restart of the client is causing users to rage at being forced to literally stare at a queue (my own personal experience btw of sitting in a queue of 4k+ just to have to crash at 628 when I opened a Youtube tab then quickly logging back in to get my spot).

If people could feel confident walking away I think that would solve a large amount of issues. It is already saving your spot so why not just keep the client open and try a reconnect from there instead of requiring a fresh login and reconnect praying you can even make it that far.

[Seraphor]

So the core issue is the single attempt before tanking the client. Requiring a complete restart of the client is causing users to rage at being forced to literally stare at a queue (my own personal experience btw of sitting in a queue of 4k+ just to have to crash at 628 when I opened a Youtube tab then quickly logging back in to get my spot).

If people could feel confident walking away I think that would solve a large amount of issues. It is already saving your spot so why not just keep the client open and try a reconnect from there instead of requiring a fresh login and reconnect praying you can even make it that far.

But you just said, using a vpn prevents 2002 errors, so no need to babysit the queue.

Indeed the 2002 error has been fixed on EU servers, I haven't had one since the patch.

[Medura]

Wait, where have they ever blamed consumers internet connection on 2002? Thats 90002 mate! 2002 is when there's too many people in quehe at the same time for the login server to handle, thats why they increased the amount the quehing servers could handle, clearly not enough, but it did help quite a bit.

[Puremallace]

Wait, where have they ever blamed consumers internet connection on 2002? Thats 90002 mate! 2002 is when there's too many people in quehe at the same time for the login server to handle, thats why they increased the amount the quehing servers could handle, clearly not enough, but it did help quite a bit.

https://na.finalfantasyxiv.com/lodes...9264ac9f24986f

Error 2002 Occurrence From Issues With the Player's Internet Connection

Currently, most of the reports we have been receiving about Error 2002 are to do with this issue. The reason for this is that, as a result of longer queues and more time spent in the queue, there is an increased likelihood of issues occurring in relation to the player’s internet connection. In most cases, this is considered to be caused by packet loss on the internet route or instability from the Wi-Fi connection in the player's internet environment.

[Havenchild]

People either have reading comprehension issues or they just pretending to not read to be upset. They have blamed 2002 on two distinct issues.

Verbatum they did say:
Occurrence of Error 2002 When the No. of Players Waiting in the Queue per Logical Data Centre Exceeds 17,000
Error 2002 Occurrence From Issues With the Player's Internet Connection

The only thing this document proved, is that the first cause is operating beyond what they have defined and that "refresh" actually counts as a re-queue as well. Whether that is intentional or not, who knows but I'm leaning towards yes to prevent the login servers from going down. I've only got a 2002 error, when usually otherwise it would do that Queue Box reload which I'm assuming was a "refresh".

But that also explains why at 12AM EST, I have counted down from an 8k queue to 0 and got in with "0" 2002 errors whereas during 8PM EST, I counted down from 5k and got "4" 2002 errors. Literally the servers are not reaching 17k around the clock but only during prime time.

I think that first cause always made far more sense than the latter considering my own experience when logging in at different times of day but both still can apply for each individual logging in.

[lezard21]

Someone on reddit was nice enough to do a full technical analysis of the cause of the 2002 error and JUST LIKE everyone has been saying.

The server is resetting you client every 15 minutes and if it desyncs during this client reset it crashes the client.

This has nothing to do with your internet but an internal server side check done once that causes you client to crash.

Fix this now and stop blaming your consumers for internal coding issues.

https://docs.google.com/document/u/0...jk/mobilebasic

Source: reddit user u/pitiful-marzipan

After being called a Karen, insulted and threatened by the forum's fanboys and whiteknights I feel so vindicated now.

Thank you OP and whoever did the research!

[ijuakos_xqwzts]

After being called a Karen, insulted and threated by the forum's fanboys and whiteknights I feel so vindicated now.

Thank you OP and whoever did the research!

"Vindicated"? All they did is sniff some traffic and make assumptions on a behavior of their network client. While I've been able to see similar behavior (specifically, a connection close and re-establish every 15.5 minutes), there's nothing to back the assertion that a desynchronization during this reset will crash the client.

[PredatoryCatgirl]

Guess what dude: I agree with this issue and still think you're a Karen because of how you phrase your arguments and the measures you suggest people take. Being right about one thing and being a whiny baby are not mutually exclusive.

[Belisaire]

I was defending SE early on but this is shameful especially since Yoshi-P has been going on record blaming consumers internet connection.

I've been with the game since 1.0 and have seen ups and downs but haven't seen Yoshi-P straight up misdirect like this. I'm also concerned that Square-Enix's angle seems to be to just pray the issue goes away.