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

[Kotisimus]

the process does work or no one would be able to log in period

This is false, getting error 2002 doesn't prevent u from playing the game. It prevents u from logging into the game server IF u are not quick enough to just rejoin the queue.

or no one would be able to play...period.

Incorrect for the same reason above.

software either works or it doesnt

Again incorrect, software is not an ON/OFF switch, it can work and still have multiple bugs/issues. Please stop making assumptions based on ur own experience when u clearly got no idea.

[Kes13a]

This is false, getting error 2002 doesn't prevent u from playing the game. It prevents u from logging into the game server IF u are not quick enough to just rejoin the queue.

yes, but if it did not work AT ALL, then everyone would get 2002 and no one could log in. there are those that do not get this error. therefore, it is conditional. point out how that is "false"

Incorrect for the same reason above.

please feel free to post the entire part where I said, once in, the 2002 error would prevent you from playing?

Again incorrect, software is not an ON/OFF switch, it can work and still have multiple bugs/issues. Please stop making assumptions based on ur own experience when u clearly got no idea.

did you even read and understand what I said?

I said, there is some condition being met that prompts the 2002 error. if software runs into a certain condition, it will error. not everyone is seeing this error. so a condition is being met which drops the connection. this does not happen for everyone. it is possible, can the software work with a bug, it certainly can, but the programmers have a running joke about bugs and errors being caused by "unintended application" which means the user is doing something outside the regular recommended workflow. in this case, something in the connection is causing an unintended response.

no need to be antagonistic, I am in no way saying its not a code issue, there are issues with their code no doubt. just pointing out that it seems consistent for some, but not all. which leads me to suspect its more than just bad code. good to know your first forum post was so benign. I get it, you are frustrated, a lot of people are.

[Kotisimus]

yes, but if it did not work AT ALL, then everyone would get 2002 and no one could log in.

And i repeat again, getting 2002 DOES NOT prevent u from logging in. It just disconnects u from the queue and u can jump back in at THE SAME position if u are fast enough to do so. So u are absolutely wrong when u state that "no one could log in".

please feel free to post the entire part where I said, once in, the 2002 error would prevent you from playing?

You just said

then everyone would get 2002 and no one could log in.

Which is incorrect.

did you even read and understand what I said?

Yes, hence the suggestion to stop making assumptions when u clearly got no idea.

but the programmers have a running joke about bugs and errors being caused by "unintended application" which means the user is doing something outside the regular recommended workflow.

Me and my wife are playing over the same internet provider using exactly the same router from the same apartment. She will have error 2002 while i wont and in 1 hour i will have it and she wont. So i got no idea what the SE's "intended application" of their software is, but my wife and me where clearly using it as intended prior to EW since we were never getting error 2002 back then and suddenly we are NOT using it as intended after EW launch. Your logic is just flawed.

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

[Bertpocalypse]

Masterminds at SE making desync algos to secretly sanitize session data from the login queue so their new game can look more popular - fooling the masses!

...they thought it was the perfect crime... BUT THEY NEVER SUSPECTED... WIRESHARK ANDY WITH HIS SIDEKICK BASIC FILTERING

[MiaShino]

Masterminds at SE making desync algos to secretly sanitize session data from the login queue so their new game can look more popular - fooling the masses!

...they thought it was the perfect crime... BUT THEY NEVER SUSPECTED... WIRESHARK ANDY WITH HIS SIDEKICK BASIC FILTERING

Oh my oh my! What a useful and constructive post detailing how the aforementioned google doc is completely and utterly incorrect.

[KihraJhin]

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

Imagine if we had a proper queue. Like once you queue your id gets put in the queue. and once it reached first place (or at least the group that designated to enter next) it should check if said client is actually connected and then boot you if it isnt. that way any amount of 2002 up to the point at least would not kick you.

[Araxes]

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

It is the same thing with the 90k Errors.
They also try to blame us for that. I had them quite a lot and it was never my Connection cause every other Service was still online.
To negate their claims further: The mass reports of 90k Errors started with Endwalker. It would be kinda rediculous if the internet of a lot of people suddenly goes down the toilet because the Expansion of a MMO launched.

[Bertpocalypse]

Oh my oh my! What a useful and constructive post detailing how the aforementioned google doc is completely and utterly incorrect.

i was going more for the conjecture theme tbh.

i wont deny there are problems - i don't think the intended message from the response regarding packet loss exacerbating issues with the lobby server was "blaming it all on macdonalds wifi - its not our fault at all".

i can never know how imperfect the login process is because i'm not sitting on the lobby/game/whatever servers code. its apparent in the document that neither is the author. there are alot more moving parts than just "highfives" to the lobby - the googledoc had me until it started making baseless opinions in this regard using a couple fin packets to prove the client wants a refresh.

my comment is more for the people buying into a conspiracy that SE is purposely sabotaging its own game while gaslighting its users.

[MiaShino]

i was going more for the conjecture theme tbh.

i wont deny there are problems - i don't think the intended message from the response regarding packet loss exacerbating issues with the lobby server was "blaming it all on macdonalds wifi - its not our fault at all".

Ohhh aye, that is not what I got from Yoshi P's posts either.

i can never know how imperfect the login process is because i'm not sitting on the lobby/game/whatever servers code. its apparent in the document that neither is the author. there are alot more moving parts than just "highfives" to the lobby - the googledoc had me until it started making baseless opinions in this regard using a couple fin packets to prove the client wants a refresh.

It appears to be issue that primarily exists on the server end though can manifest on our end too. Attempting figuring out how their servers actually operate is umm, well it is not worth it. Endlessly sniffing packets back during the WoW emulator days was some of the most grueling and tiresome work I have ever ever done. The best we could do was "approximate" their back end stuffs and it was hell.

my comment is more for the people buying into a conspiracy that SE is purposely sabotaging its own game while gaslighting its users.

Yup yup, I can agree with this. I see what is occurring more as general incompetence than grand conspiracy myself, which is staggeringly common in the field of system administration. Many apologies if I misunderstood your intent!

Reading Yoshi's post reads more as if he is suggesting to the user that they eliminate anything they can on their end so not to wait in more queues. It does not help that his language is JP and it doth not translate well to English.