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

[Viirin]

Someone on reddit was nice enough to do a full technical analysis of the cause of the 2002 error...

So, first of all, thanks for sharing this, it's really interesting and its good to see someone posting something of actual value rather than just complaining.

It is actually pretty astonishing to me that the server would drop the connection every 15 minutes and force a new connection. I'd seen a few people claim they were getting 2002'd every 15 minutes and I was pretty skeptical because it didn't seem there would be any reason for the server to drop people from queue in 15 minute increments. But, this data does seem to indicate that's the case, not that it's dropping them from queue intentionally necessarily, but it is introducing the chance for it to happen for no apparent reason.

I do think you're oversimplifying a bit with some of what you say here. 2002 doesn't have nothing to do with the user's internet connection. If there is a problem with the user's internet connection, they will certainly see this error. But, it's definitely also fair to say that probably most of the errors that people are seeing don't have anything to do with their internet connection. I get these errors every time I have to sit in a queue, and I've always been on a wired connection. It also begs the question of why everyone experiences these 2002 disconnects but almost everyone has no problem maintaining a connection to the game once they're logged in if the problem is bad internet. Why can I hold one connection for many hours without issue, but can't with another connection?

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.

The chip shortage is the reason we're seeing this issue as badly as we are right now. Since the issue is something that appears in 15 minute iterations while in queue, if you're in queue for less than 15 minutes, you'll never see it, even though the issue exists. If you're in queue for 15-29 minutes, you'll still probably not see it all that often, since it's not a 100% chance you'll lose the connection. But if you're in queue for hours and hours you're going to start seeing it a lot.

Previously, they could get by without fixing the login queue code, but that time is behind us. Not fixing this is going to cost them. They can buy themselves time by extending subscriptions, which I can't believe they still haven't announced anything beyond the original 7 days.

If a small interruption in a connection is all it takes to be kicked out of queue, the coding is bad. The client doesn't need to close. It should just keep retrying until it gets back in.

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

Based on the data provided, I'd say part of the problem does exist on the user's end, in the game client that the user has no control over. It should be trying to reconnect, not simply give up and exit itself.

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.

I don't think that Yoshi-P is lying, I think he believes what he has said. It's doubtful that he has a technical understanding of what is happening with the login queue and he is going by information that he has been from the people who do (or are supposed to, as the case may be).

As time goes on, I begin to also have a concern that they aren't addressing the issue with the login queue code.

We'll see what happens... As I've said elsewhere, it is what it is. My advice to everyone is the same as what I'll do myself - if the next time your subscription renewal is about to happen, you feel like you aren't getting your money's worth, cancel your sub and wait until you hear the situation is improved.