Please fix the grace period while in queue

[FFVIXRhay]

Yeah happened here as well. Literally got to 1 in the queue, got the lobby error back to back 3 times, logged in on the 4th attempt to a 6k+ queue. Rip lol.

Happened Here to. Got 1 queue for like a 3-4 hrs then i got the 4004 . queued again got around 8k

[jadan2000]

The level to which we are having issue was definitely not explained well enough in their congestion message to the community. They are putting us through a very frustrating situation. i would much rather click the start button and be told, i cant get in queue, then to press the start button, get in queue, and then get kicked out and have to start over at the end of the line... if i can get back in queue..

[Akava]

A buddy of mine and his gf both had horrible times getting logged in today as well and we didn't find out until they finally got on. He was trying to log on for a total of 7 hours with a total of 5 queue resets. His highest position in queue being over 6,000 and her's around 5,800.

I know a lot of people are angry at people who used to avoid the auto-logoff feature but this kind of experience can quickly push someone down that path. They fixed the loopholes but didn't address one of the major frustrations that made people want to avoid the queue in the first place.

[Yureina]

I was 14 in queue and got the 4004 error... now back to 2.6k.

This is absurd and depressing.

[Kukra]

I had my place saved with the 2002 error, but when I get the 4004 error it boots me back to 4k.

[Havenchild]

I have never successfully seen a queue time below say 20 ish and it actually resolve in this game over the last 8 years. Usually the queue resolves closer to 27 and then in jumps you in (although I have seen disconnections when it changes to the Now Loading screen). I am fairly sure that when your queue is below that number you have infact lagged out of the queue and there is a high chance you disconnected.
That's just my experience since beta but I can't say I've ever seen a #1 or even digits in the 10s, ever.

[Seera1024]

I have never successfully seen a queue time below say 20 ish and it actually resolve in this game over the last 8 years. Usually the queue resolves closer to 27 and then in jumps you in (although I have seen disconnections when it changes to the Now Loading screen). I am fairly sure that when your queue is below that number you have infact lagged out of the queue and there is a high chance you disconnected.
That's just my experience since beta but I can't say I've ever seen a #1 or even digits in the 10s, ever.

You may not have experienced it, but for you to be at 27, someone else has to be at 1.

[Havenchild]

You may not have experienced it, but for you to be at 27, someone else has to be at 1.

In theory yes, but I have never seen this to be true, whether watching friends, streams, myself log in. Yes a rather small sighted opinion, but one I think is corroborated by the fact so many people that supposedly have these "lower" numbers especially those seeing #1-10 are greeted by immediate or soon after disconnects.

Think of this at a different level, let's think pre expansion a sec, even before the WoW exodus, at the deadest of hours EST. I would still get a queue of maybe the lowest 17. It has never been instantaneous but perhaps resolves in 5 seconds or so. Incidently, I've had the same number "ahead" of me during supposed peak times. The odds that there are that many people ahead of me, in that consistent same amount regardless of time, has always lead me to believe that 17-27 is a placeholder value for the "next in line". Call it theory or gibberish but hey that's just been my experience playing since beta.

I stand by the claim that if you go any lower than that, there is a high chance you've already been disconnected or at the very least, lost packets and the countdown proceeded regardless, before re-establishing a legitimate connection.

[Yureina]

It happened to me again... another 4004 error when I reached 21 in the queue... now back to 1212.

[skyfox]

programming 101. When there is an error a.k.a. exceptions, it needs to be handled or it will throw an error and shit itself. Just have to remember the queue# of "x" and put "x" back in to the same queue# he was at. Dev seems already done this part but they forgot to handle the exception when there is packet loss between users and the lobby server, it throw an error and kick user out of lobby reset queue# (i.e. error code 2002). I can understand why they set the max queue size to 17000 but I am not sure why they coded lobby server to reset queue# due to the packet loss.