Apparently you guys don't read else you would have known that the quite below is correct.. Stop freaking out this is intentional when servers come up after maint...
Quote:
Originally Posted by Ptolemy
1017 rears its ugly head again
Printable View
-
09-20-2013, 10:27 AMxwmstormx
-
09-20-2013, 10:28 AMKesac
Most likely it's because only 500 people can be queued at once, and since the servers aren't up everyone's bombarding that 500-person queue. Once the servers come up 1017 should disappear quickly....(Note: I just got a queue on Balmung, 79 people....let's hope it doesn't go to error 90000....)
EDIT: In game now -
09-20-2013, 10:29 AMRinoaHeartilly
Yup I'm getting it on Leviathan for the first time since two weeks ago but I agree it must be because it's right after maintenance .
-
09-20-2013, 10:30 AMTaliph
ITT: people who don't understand that an error code is not a bug to be fixed, but a symptom of an occurring issue (hint: that issue is login throttling, and working as intended)
-
09-20-2013, 10:33 AMAlmaMalma
So, after the expected deduction in players once the charges came in, SE have reduced the number of active signons.... but too low. GG SE. Still, they got our moneys for signing on for 30 or more days. Mug {you can have this}.
-
09-20-2013, 10:34 AMPoyozoSo its 30 minutes since maintenance ended. That means I have to wait whenever the hell they deem it appropriate for me to log in? So I guess the maintenance is unofficially an hour or more longer than they said.Quote:
Originally Posted by xwmstormx
-
09-20-2013, 10:34 AMEvokerKeii
If maintenance didn't happen during PRIME TIME then there wouldn't be a million people shoving themselves into the login server at once.
-
09-20-2013, 10:34 AMZyeriis
Sigh, really?
-
09-20-2013, 10:37 AMSartoriSo.....Is it intentional for me not to be able to leave my Inn room?Quote:
Originally Posted by xwmstormx
-
09-20-2013, 10:38 AMZyeriis
Got into a queue! Hurray! ...wait, 1017'd again anyway. The fuck...