The server is full, try again later (1017)

[Sezuel]

Apparently what most of you dont realize is that there WAS a queuing process ... at least there was before the maintenance that went from 08 00 GMT to 11 00 GMT (which is when I chose to go to bed)

[Quixadhal]

Apparently what most of you dont realize is that there WAS a queuing process ... at least there was before the maintenance that went from 08 00 GMT to 11 00 GMT (which is when I chose to go to bed)

OH we realize it. That's part of the reason we're so angry.... they had a queuing system, but they capped the QUEUE, thus adding insult to injury. So, you have to spam login attempts to try and get into the login queue, where you sit and wait. Yeah, who's brilliant idea was that?

[seebs]

Apparently what most of you dont realize is that there WAS a queuing process ... at least there was before the maintenance that went from 08 00 GMT to 11 00 GMT (which is when I chose to go to bed)

No, I realize that. That is precisely why I'm irritated. I know SE has at least heard of queueing. That means that 1017 errors are a severe regression. That error should not even exist -- there should be no such thing as "world full, can't log in", only "world full, entering queue". They made something dramatically worse, and have offered no explanation, no rationale, not even an acknowledgement that this is a change and that it is a bad change.

[1HotKitten]

Apparently what most of you dont realize is that there WAS a queuing process ... at least there was before the maintenance that went from 08 00 GMT to 11 00 GMT (which is when I chose to go to bed)

Their queueing process sucks tho. It must have a max # of chars it can handle, because if you are LUCKY you might get in the queue, but most of the time you just get the ridiculous 'world is full' error and have to keep trying and trying. That is, like others have mentioned, the HEIGHT OF STUPIDITY. Get a clue, SE, create a decent queueing process.