Im pretty sure that if you get 2002'd and your spot in line is ready to load into the game while you are still trying to reconnect to the lobby server your spot is lost and you are sent to the back of the line. This has happened to me 3 times.


Im pretty sure that if you get 2002'd and your spot in line is ready to load into the game while you are still trying to reconnect to the lobby server your spot is lost and you are sent to the back of the line. This has happened to me 3 times.
Problem is when you keep getting errors when trying to connect again, and then it's too late :P



There have been times when I have been 2002'd and logged in immediately after, and not gotten my place back. However long the timer is, its not long enough. Unlike the chip shortage, this is within SE's power to fix.




not sure what the timing is, but I have gotten the 2002 error a couple times since redoing my internet at home, and get my spot back. cant say why its not working for you
could be size of teh queue maybe? hard to say
The issue is that if you get 2002'd in q, then cant even get back to the q for 3-4 tries because more 2002, and for some reason the lazy ass engineers decided that a log in failure should require a complete relaunch of the game, it takes more than the "tens of seconds" it holds your spot for.
They could fix this, all I am hearing is excuses because SE doesn't want to spend the money. They know in 2-3 months the subscriber base will drop away and they don't want to invest now, they would rather ride it out. Everything they are selling us is bull.



EVERY SINGLE MMO has data clientside. Saying that it had anything to do with New World failing is like talking about the food served on the Titanic.


For now, I'm willing to believe there may be some logical, if abstract, reasoning for why they can't increase the reservation timer. Most often, when an "obvious" solution isn't being implemented, it'll be because they, too, have already thought of it and determined some impracticality. If the login servers are struggling because they're overloaded, then saving a spot in line for everyone erroring out is counterproductive to the server erroring everyone out. They'd just need to make a new error to keep from getting stuck in the old one.
Or something dumb/weird like that. Cuz, seems more irrational to believe they could be extending the timer but refuse because they just don't care or whatever.
Sure could be. I work at a software engineering company and it's simple to make excuses when you do not want to get out of your way with customer requests. It probably involves other work/QA/whatever that they do not want to deal with right now.For now, I'm willing to believe there may be some logical, if abstract, reasoning for why they can't increase the reservation timer. Most often, when an "obvious" solution isn't being implemented, it'll be because they, too, have already thought of it and determined some impracticality. If the login servers are struggling because they're overloaded, then saving a spot in line for everyone erroring out is counterproductive to the server erroring everyone out. They'd just need to make a new error to keep from getting stuck in the old one.
Or something dumb/weird like that. Cuz, seems more irrational to believe they could be extending the timer but refuse because they just don't care or whatever.
I also work in software engineering as an architect and full stack developer. You're spot on.
|
|
![]() |
![]() |
![]() |
|
|
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





