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

[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.

[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.

[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.

[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.

[Zanarkand-Ronso]

After being called a Karen, insulted and threated

Ok Karen Calm down....Just because you feel good about yourself doesnt mean you get to oversell things.
Besides, you were called a Karen for your attitude, not for addressing an issue everyone has faced. Some worse then others.

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

That quote of yours does not 100% Directly Blame peoples Internet connections. But suggests that Internet Connections also effect the issue.
Client resets are also a result of Packet Loss if Im remembering that correctly, which is also effected by your internet .
So its not a Complete BLAME of my internet or your internet or somebody else internet.

Also, reading the Analysis (Or what I can personally understand) there is a claim that every 15 minutes the Error 2002 happens mid-queue and just randomly kicks you off......I can say this is false, or this might be something that effects some people. Because I time how long it takes for me to get on, and I do not face a Random Kickoff every 15 minutes. Not even on release when things were at their worse.

[Macleod]

Also, reading the Analysis (Or what I can personally understand) there is a claim that every 15 minutes the Error 2002 happens mid-queue and just randomly kicks you off......I can say this is false, or this might be something that effects some people. Because I time how long it takes for me to get on, and I do not face a Random Kickoff every 15 minutes. Not even on release when things were at their worse.

It's not saying you get kicked off every 15 minutes, it's saying you have a CHANCE of getting kicked off every 15 minutes if you fail to re-establish the connection in their convoluted queue system that force disconnects you and attempts to reconnect in the background. You won't know it failed until you get Error 2002. If you successfully reconnected, you'll never know it happened. This is something the queue should not be doing, we're already connected and in queue...keep us connected.

[basilbc]

That quote of yours does not 100% Directly Blame peoples Internet connections. But suggests that Internet Connections also effect the issue.
Client resets are also a result of Packet Loss if Im remembering that correctly, which is also effected by your internet .
So its not a Complete BLAME of my internet or your internet or somebody else internet.

To be fair, it says "Most of the reports we have received", which is a distinction I personally wouldn't make if the situation is not definitive. Probably would've stuck with "some".

I don't think it's malicious but it's definitely something that can easily be misconstrued!

[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.