Why the queue is not being fixed ?

[Crashdummy]

The queue isn't malfunctioning, it just doesn't work the way you think it works.

There is a hard limit on simultaneously logged in players. Once this limit is hit, you get 1017s.

Once a certain number of people have logged out, the restriction is lifted and floodgates opened, but the server can only process logins so fast. So in the case where a ton of people try to log in simultaneously, this is when the queue kicks in.

This is wrong. The queue IS malfunctioning. Hell, i have even BEEN in the queue only to get KICKED of it after 30 seconds. How is that functioning well?

Please stop trying to defend this, the queue IS NOT WORKING.

The point of the queue is that when people cant log in because the server doesnt have space, they get into a queue.

Spamming a connection request not only makes people rage, but also generates more work to the server.

[EinherjarLucian]

This is wrong. The queue IS malfunctioning. Hell, i have even BEEN in the queue only to get KICKED of it after 30 seconds. How is that functioning well?

Please stop trying to defend this, the queue IS NOT WORKING.

The point of the queue is that when people cant log in because the server doesnt have space, they get into a queue.

Spamming a connection request not only makes people rage, but also generates more work to the server.

Correct, the queue is not working properly. You can be in the queue, given a place in line, then suddenly get a 1017 error and have to start all over again. That is not proper behavior for a queue, even a little.

My guess is that the "1017" error is being returned whenever the server either returns Connection Refused or Service Unavailable. The client sees this (reasonably so) as an error condition. The bug, however, is that the client doesn't retry to update its queue position after getting such an error; it instead returns to the lobby screen. The fix is for the client to realize it's in a queue state, and that it should attempt to retry.