We paid for early access but it turned out to be NO ACCESS. PAY OUR MONEY BACK

[Darkstride]

The only thing im annoyed about is the continuous 2002!errors after waiting in long ques.

It's annoying but it's just the servers being overloaded. They made a post pre-early access specifically to address that it would be a concern.

“Error 2002” may be displayed when selecting a character in the Character Selection menu. This error is displayed when the login server is experiencing high amounts of traffic or when the number of characters waiting in a login queue for a logical Data Center exceeds 17,000. This is a measure to prevent the server from crashing due to extreme traffic overloads.

Should you encounter Error 2002 when attempting to log in, we apologize for the inconvenience, but ask that you wait a while before trying again."

[HirokiR]

What I find a bit odd is that SE's sites and posts say the long queues are fine and working as expected, but I, and I'm sure a helluva lot of other people, keep getting the 2002 boot either before login queuing or during, like after a few hundred. So all is dandy, yet the queue spots keep resetting... So... Is that a expected behavior for a countdown?

[Unaki]

It would be so nice if it would stop booting me after 30 minutes in the queue. If I'm going to be doing other things at least stop making me have to babysit the game.

[Darkstride]

What I find a bit odd is that SE's sites and posts say the long queues are fine and working as expected, but I, and I'm sure a helluva lot of other people, keep getting the 2002 boot either before login queuing or during, like after a few hundred. So all is dandy, yet the queue spots keep resetting... So... Is that a expected behavior for a countdown?

From what they posted, it seems like if the Data Center queue exceeds 17,000 then the error 2002 is a failsafe to prevent an overload. They had added a "visit another world" option that would automatically filter you to another server to reduce queues, but it fails when I select the option. I'm assuming that's because the data center queues are heavy across the board.

[Vimzu]

I think they should have taken longer than a two week delay to launch Endwalker, getting through to the actual server is the savage content, you are meant to only get a 2002 error when the login queue for the Data Center exceeds 17,000 but every time I manage to get into a queue it is under 4,000. The login server isn't capable of handing the login requests.

I think if you have 24 million active users and your data centers in EU, Japan and USA have a theoretical limit of 17k then you aren't ready for an expansion where a lot of those users who irregularly log in are all piling on at the same time, the game was unstable with server issues before Endwalker, we just have increased the problem tenfold with the expansion. You are effectively DoSing your own login server, because people can't connect and they keep trying to reconnect whenever they lose connection.

It is an archaic way to handle server/client interaction. When you login, the data center should assign your client/account a queue position and it should initiate the connection when it has capacity to handle you logging into the game and it can give your account a grace period so if your client crashes or whatever it shouldn't impact your position in the queue.

Being in a queue for an hour and then getting dumped out with a 2002 error message when you enter the queue at 2500, there are issues beyond physical server limitations. How is it possible that queues are both so short and instability is so high?

[Darkstride]

the login queue for the Data Center exceeds 17,000 but every time I manage to get into a queue it is under 4,000. The login server isn't capable of handing the login requests.

Isn't the queue number that you're seeing specifically for your server, whereas the Data Center limit would be for the servers collectively?

[Rizon]

While I understand where the OP is coming from this should have been foreseen by the player base. There hasn't been an expansion yet that has not been fraught with problems of one kind or another. All Early access is good for is to QA for the servers that should have been performed well in advance of launch. This time it started with the launcher being FUBAR at the onset of live play. It has now morphed into constant 2002 errors when trying to access the data server (just happened 7 straight time to me). When this happens the game is immediately closed and you have to start all over again. If y6ou are fortunate to get past this then you are greeted with a character screen with no character info except for the character name. Upon selecting your character you are met with a que that averages around 2700, in my case. To add insult to injury you stand a 70% chance of getting the dreaded 2002 and have to start all over. Is this any way to run a railroad? Advise for Yoshi-P. Before you release 7.0 you need to conduct an in-depth study of server requirements and plan accordingly. Unfortunately at my age (74,5) I'll be lucky to be around for that launch which is why I was hoping this one would go much better.

[Pierdo]

I think more to the point is that you shouldn't be requesting a refund for "early access" but for Shadowbringers entirely. I doubt the playability is going to increase by release. It seems like the only thing that'll solve the problem will be more server hardware.

I think everyone should be inundating SE's support with refund requests for shadowbringers because why pay for a game that isn't playable?

[jadan2000]

to me the issue really is the spontaneous 2002 errors. getting those while you're in a very long queue is just not ok. we should be able to stay in queue. If you cant keep us in queue then just tell us the servers are full and we cant log in so we dont keep trying.

[Vimzu]

Isn't the queue number that you're seeing specifically for your server, whereas the Data Center limit would be for the servers collectively?

True, that is probably the individual server queue, we aren't seeing the entre data centre queue.

I am not sure why we are being hit with 2002 error whilst already in the queue for some time though, it should only impact people attempting to get into the queue.