Emergency Code Fix Required

Its one thing to wait in a line for hours.

Its another thing to wait in a line for hours to get disconnected in a way that isn't your fault and end up starting over again and to do that repeatedly over the course of 14 hours.

It is inexcusable that a 2002 error does not reserve your place in line if you reconnect within 5 minutes, and there is no reason this can't be solved by a code fix.

It does hold your place in line though not sure the exact time length but as long as your paying attention and requeue after it will put you back where you were.

Quote:

---

Originally Posted by Rita1989

It does hold your place in line though not sure the exact time length but as long as your paying attention and requeue after it will put you back where you were.

---

Its less than 3 minutes.

I was setting at number 1 in queue for about 5 minutes, got the 2002 error, logged immediately back in, couldn't have taken more than 20 seconds, to a queue of 800+

I've reconnected 3 times within 30sec of getting the error of my disconnection and it did not hold my place in queue a single time.

Quote:

---

Originally Posted by say0

Its less than 3 minutes.

---

False. I've gone over 4 and gotten my spot back.

Keep trying OP, you'll get in!

Quote:

---

Originally Posted by Rita1989

It does hold your place in line though not sure the exact time length but as long as your paying attention and requeue after it will put you back where you were.

---

Having experience countless 2002 errors since 1AM of Dec 3rd, I can tell you with absolute certainty and confidence that it does not hold your place in queue 99% of the time. It doesn't matter if you log back in within 3 minutes or 15 seconds, it does not hold your place. And that 1% of the time it seems like it has? That's because all the other 17k people that led to the 2002 error also got dumped and you just so happened to jump back in at the right moment to be within a few places of where you were before.

This has been pointed out by so many people at this point that it baffles me that people actually believe this is working.

Quote:

---

Originally Posted by CazzT

Having experience countless 2002 errors since 1AM of Dec 3rd, I can tell you with absolute certainty and confidence that it does not hold your place in queue 99% of the time. It doesn't matter if you log back in within 3 minutes or 15 seconds, it does not hold your place. And that 1% of the time it seems like it has? That's because all the other 17k people that led to the 2002 error also got dumped and you just so happened to jump back in at the right moment to be within a few places of where you were before.

This has been pointed out by so many people at this point that it baffles me that people actually believe this is working.

---

It may be dependent on the cause of the crash.

On Friday the second time I got booted to the desktop from a 2002 error, I decided to try to log in to a character on another server to see if that queue was shorter. It wasn't. I went back to the character I was initially trying on and was back at about the place I got booted from. Given the time it took to do all that, if my place had not been reserved, I would have expected to be higher in queue. As I had crashed to desktop, I wasn't expecting the game to hold my place in line which is why I attempted to log into a second character to see if I could get in.

My theory is that a two-factors authentication prevent you from getting you spot back in queue. I think that re-entering the 6-digit code regenerate a new credential token that the login server interpret as a new player, henceforth putting you back at the bottom of the queue.

Maybe people that have managed to keep their place in queue can share whether they use a two-factors authentication ?

Personally, I do use the two-factors authentication and have never managed to keep my spot in queue after re-logging, even after re-logging in less than 30sec.

Quote:

---

Originally Posted by dutiona

My theory is that a two-factors authentication prevent you from getting you spot back in queue. I think that re-entering the 6-digit code regenerate a new credential token that the login server interpret as a new player, henceforth putting you back at the bottom of the queue.

Maybe people that have managed to keep their place in queue can share whether they use a two-factors authentication ?

Personally, I do use the two-factors authentication and have never managed to keep my spot in queue after re-logging, even after re-logging in less than 30sec.

---

That's not the cause of the dropped position.

I lost my position after my first drop on Friday. I do not have the 2 factor authenticator on the account.

Edit: Or at least that's not the 100% cause of it. You aren't going to guarantee keeping a spot by not having it.

it is weird, the get back in your spot after 2002
I dont have two-factors authentication, sometime I got kick back at the queue even I re-log in right after the 2002
sometime I get my spot back even a minute or 2 over the 2002
anyway, 2002 error is a bigger issue than queue, long queue are expected and we will eventually get in. the randomless of 2002 just mean queue at 1000 or 10000 make almost no difference

Quote:

---

Originally Posted by dutiona

My theory is that a two-factors authentication prevent you from getting you spot back in queue. I think that re-entering the 6-digit code regenerate a new credential token that the login server interpret as a new player, henceforth putting you back at the bottom of the queue.

Maybe people that have managed to keep their place in queue can share whether they use a two-factors authentication ?

Personally, I do use the two-factors authentication and have never managed to keep my spot in queue after re-logging, even after re-logging in less than 30sec.

---

I use 2FA and can add my own experiences here.. If you get a 2002 error and log back in within a few minutes and you reach character select screen your spot in que seems to be preserved, however if you get a 2002 error and then get a second one before even reaching character select your position is often lost. I've also had a case where I got a 2002 error and an extra two errors before char screen but it still kept my spot, so maybe it's just a flat 3-5 minute time limit? I'm not quite sure yet, but I can confirm 2FA doesn't seem to affect it.

Thanks for your feedbacks, hopefully I'm wrong otherwise it's a gross oversight on their side ^^ .
There is hope :x !