The server is full, try again later (1017)

[Deadrifler]

I beat the screen once...then got a Library Runtime Error and my game crashed. T_T

[Sadebreth]

How the queue and how it's working was already explained. Several times. There is in fact a queue. SE has stated they have severe restrictions in place. This means that if they restricted the server to 1000 players (random number), and if there are already 995 players online, and you are 25th in queue, the first 5 players will get in and the manual limitations will kick all the rest from the queue. When the server opens up slots individuals will be able to see the queue system again as the process repeats.

How does this explain people that get into the que and then get booted from it. If you are able to get into the que then you should no longer be part of the restriction. If that is the case then they did some piss poor math on how many people they are allowing in the que to begin with.

[Fynarra]

The part about it all that really bothers me is the number of clicks and screens you go through to GET the 1017 error. Seriously--if you're going to throw an error rather than put us in queue (and throw us OUT of queue), make the return screen the same character select page you left from rather than all the way back at the lobby x.x

[Faustt]

to me even if the servers were up right now I am still considering canceling my game. Just shows me what to expect from this half assed company, it's no wonder this company is in so much trouble, I know a few western devs that worked with them, they all said they are retarded.

[Raist]

How the queue and how it's working was already explained. Several times. There is in fact a queue. SE has stated they have severe restrictions in place. This means that if they restricted the server to 1000 players (random number), and if there are already 995 players online, and you are 25th in queue, the first 5 players will get in and the manual limitations will kick all the rest from the queue. When the server opens up slots individuals will be able to see the queue system again as the process repeats until SE decides to stop throttling.

They are throttling to test server capacity and load; which imo should have been done in Beta P4.

But that's not right either. Once you are in the Queue... you should stay in that queue until you back out of it. What appears to be happening now is people are just getting bounced from queue just before logging in, or they are geting flat out rejected all together.

Ideally when using a login queue, there should not be a Full Server rejection message unless you are trying to create a new character on that server---not when trying to log in with an established character.

[Sadebreth]

But that's not right either. Once you are in the Queue... you should stay in that queue until you back out of it. What appears to be happening now is people are just getting bounced from queue just before logging in, or they are geting flat out rejected all together.

Ideally when using a login queue, there should not be a Full Server rejection message unless you are trying to create a new character on that server---not when trying to log in with an established character.

^^^^^^
This!!

[Syrehn]

How does this explain people that get into the que and then get booted from it. If you are able to get into the queue then you should no longer be part of the restriction. If that is the case then they need they did some piss poor math on how many people they are allowing in the que to begin with.

This perfectly explains how the queue is currently functioning. It's all because of the manual limitation that SE has set. If they set a manual limit of the server being only able to hold 1000 players and there are 995 online, you login and get the queue at 25th spot, because of the manual limitation SE placed, once those last 5 slots fill up the queue vanishes leaving everyone else to restart the process.

My best guess would be that this will stop happening with the queue once SE removes their "Severe restrictions".

[Sadebreth]

This perfectly explains how the queue is currently functioning. It's all because of the manual limitation that SE has set. If they set a manual limit of the server being only able to hold 1000 players and there are 995 online, you login and get the que at 25th spot, because of the manual limitation SE placed, once those last 5 slots fill up the queue vanishes leaving everyone else to restart the process.

My best guess would be that this will stop happening with the queue once SE removes their "Severe restrictions".

Then as I said before they did some piss poor math on how many they are letting into the que in the first place. It should know how many people are already on the server and how many it can even let into the que. It shouldn't let you into the que and then boot you after the servers gets full again. That defeats the purpose of even having a que. That's why I don't believe that is what is happening.

[Lunakey]

Squerror-1017ix Presents: Login Fantasy 14: A Realm Stillborn.

[ProjectBlackRai]

I've been trying for an hour now. I got into the queue, then got booted from it. Not, I get the same 1017 error and it boots me right back to the lobby. SE should really just log off all the people who are AFK in the game so that those of us who are trying to play, can.