Good job on the 2002s; Now let's fix the 90002s

Hi there, forum readers.

6.01 largely addresses the "phantom" 2002s during the login queue process. Congrats, and good work all around - points for the away team for doing all that Wireshark research and proving the case.

I'm wondering if we can also tackle 90002s. Like the 2002s, these also claim to be a connection error. They can fire instantly, with no period of lag or latency visible on the client side. And with queue depths being as they are in the more heavily visited datacenters, getting a 90002 can mean you simply aren't playing for the rest of a day.

So, let's see what data we can collect.

I've repro'd 90002s under various circumstances:

- visiting Old Sharlayan
- queueing for a Roulette via Duty Finder (oddly, this usually hits during the first boss of a zone)
- Doing lv80 8-man maps with a pre-made group

Location and activity don't seem to matter, though the 90002s pop much more frequently in congested areas or during multiplayer content.

I've had issues with 90002s for around six months. Pre-Endwalker, this used to hit about once a night. Since Endwalker it's multiple times a day. With queues being what they are, the interruptions are fatal to game time.

I've tried just about everything I can think of, up to and including a full client reinstallation yesterday. A completely fresh Endwalker client still repros 90002s.

Data collection
Is there any data end users can collect at all that will help pin down the cause of the 90002s? The game client seems to have no instrumentation, and doesn't appear to produce log files on a crash or kick. I can't tell what it thinks is going wrong when it boots me, so I can't take steps to correct it.

Are there any logs or instrumentation we could enable that would help troubleshoot this error?

Source of the error?
Can we confirm what specific circumstance causes a 90002 to be thrown?

Greater fault tolerance?
Could the client (or server) be altered to be more tolerant of whatever condition causes the code to throw a 90002? Like if it's 3 missed packets, maybe extend double that up?

Other thoughts welcome.

just got disconnected 3rd time today (in 3h of "playing" where playing was 5min - rest in queue to log in...)
I'm getting really angry, where long queue times I could understand as massive amount of ppl tried to log in, but DCs due to some game problems and STILL no reconnect option in client is a different story...

update: just got kicked 7th!!!!!!!!!! time today (during 6h of "playing" - did router reset in meantime - problem is not here, got good fiber optic connection, never had problems before last patch

I have mentioned in another thread too, but yesterday I had lots of lag every 20 min or so, while being disconnected twice during a world hunt train and the last boss of the new raid. I tried again today to play and do a pvp roulette and after 1 min as soon as we started battling the lag appeared and took a few seconds to get back to normal. One interesting thing was that I also had some lag during the first three new raids, but while I was watching the story cutscenes I did not notice any issue.