They definitely have a system in place that holds your position in queue for a limited period if you DC. I've disconnected in queue several times and every time I get back in, I've been at the same or lower position. EVERY time.

They definitely have a system in place that holds your position in queue for a limited period if you DC. I've disconnected in queue several times and every time I get back in, I've been at the same or lower position. EVERY time.
This system does not work for everyone. It has failed me multiple times. The "save your spot" thing does not always work. I have video proof experiencing it failing today after waiting hours... not that that would be needed xD
On a direct Ethernet connection, I’ve gotten in Off hours, during peak hours I either mostly crash in queue with 2002 or crash trying to connect to the data center with 2002. Pretty unacceptable not to offer a stable waiting line for people to eventually get in, even if it’s hours later, this is definitely in SE’s side and should not require new servers to fix the waiting line connection.
. I had a few times this seemed to happen on PC but I can tell you many more I was kicked to the back of the line again so this does not work every time.

That's really unfortunate. Sorry it's failed for you; that being said, it's the first time I've seen such a system in place at all during any MMO launch, and the fact it's worked consistently for someone whose internet is as garbage as mine (I very frequently randomly lose service for anywhere from 5 seconds to maybe a minute or so) is pretty remarkable.




From what little anecdotal information I've gathered, it seems to hold your position in line for a time. However, if you get 2002'd out and your position moves down to first place while the client has crashed you out, the queue sees you're not present and dumps you back into last place.That's really unfortunate. Sorry it's failed for you; that being said, it's the first time I've seen such a system in place at all during any MMO launch, and the fact it's worked consistently for someone whose internet is as garbage as mine (I very frequently randomly lose service for anywhere from 5 seconds to maybe a minute or so) is pretty remarkable.
That's some BULL.

If that's the case, then that does indeed seem pretty dumb. I don't know enough about the tech to know if it's just an oversight, or some kind of difficulty building the system in the first place that would cause that particular behavior. Regardless, I hope they're able to identify & fix whatever's causing people to lose their spot.From what little anecdotal information I've gathered, it seems to hold your position in line for a time. However, if you get 2002'd out and your position moves down to first place while the client has crashed you out, the queue sees you're not present and dumps you back into last place.
That's some BULL.




They really need to fix their crappy, crashy login server. The people all over the forums complaining about AFKers are misdiagnosing the problem. Once you're in the game, it's been mostly fine. The potato they have running in place of a login server is the bottleneck. There's no scaling implemented; they seem to have only one for the whole datacenter.
I could deal with long queue times at an expansion launch. I'm pissed as a customer because I have to constantly monitor that queue. It crashes to desktop every 15-20 minutes, needing me to resubmit my password, OTP, etc just to rejoin the queue. And if one of those random crashes happens when you're down to double digits in queue? Screw you, back of the line.
Again. Long queue times? I get it, it's an expansion launch. Constantly needing queue monitoring, crashing the client, and losing my place in line because your ancient login server doesn't scale? Fix this.
Sad they decided to blame the customer when it's pretty obviously an issue on their end.
Unless they think that 99.9% of people in the world have a bad internet connection at the exact same time for the entire last 2 days.
You get a 2002 error half the time TRYING to get into the character screen... this has nothing to do with "long time spent in queue" or any other excuses. Do a tracert, ping, WinMTR test to NTT.net (SE's North American server gateway) and you can see for yourself where the problem lies, it's the second to last hop (probably the login server) which is definitely inside their datacenter.
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.
Reply With Quote




