logged in Masamune. Kicked. Attempted to log in. Server full. Attempts to log in to NA/EU server. Unable to update NA/EU Character list.
Awesome.
logged in Masamune. Kicked. Attempted to log in. Server full. Attempts to log in to NA/EU server. Unable to update NA/EU Character list.
Awesome.
If that's how the developers implemented the queue for A Realm Reborn, its an awful design. The queue should function as a deferred callback or a long poll that sends a request out to the server and waits for a response. That is the proper way of implementing a queue on a persistent system with high traffic volume. This would allow the login servers to place you in a queue when the server is at capacity and track the requester's progress. The next time that the server responds with an update to the attached queue thread, one of two things happen your position in the queue is updated (or not if the position remains the same) or the server doesn't get a return response and knows you've quit the queue.Sadly until the newly added servers relieve the stress the only way is to put in a restriction to put people off, having thousands of people in a queue pinging the server for a "Can I get in yet" response would only make matters worse.
Error 1017 alleviates this issue slightly by putting people off spamming log-ins.
This way, it is the server that is responsible for managing when it is contacted by a client, not the client. As it stands now, everyone spamming login to try to sneak past a 1017 error is effectively DDoS'ing the login servers as it is. 1017 just stops us before we do any damage.
Wait, I'm sorry. What? As this poster above me stated the only time that a queue should ever be used is when the server is at capacity. Not to add yet another barrier to entry when the servers are under their capacity.Please understand this: the queue wasn't taken out. It's still there. The queue only shows up when the server is not at capacity, and they are still allowing people to login to the servers. The queue is a function of the login server to prevent the login server from overloading. It's basically a "line" to let people trickle into the server at set intervals.
They've done a lot of things right with A Realm Reborn, don't get me wrong. But some of the decisions that they've made are just plain lazy and short sighted.
Last edited by ZhangoSqu; 09-02-2013 at 08:55 AM.
He worded it wrong. The Queue is still there, the Queue is just full. Login and Lobby servers do not have unlimited capacity and those, when the world is full, followed by the Login and lobby servers being full, it cant put you in Queue. There's no room for you to queue, so it had to kick you out. The Queue is working, it's just overloaded by everyone that is trying to long in before you. They need to make the line somewhere or everything goes down.
That may be so, but again, it is a design flaw. There should not be a maximum size to the queue. The point of the queue is to tell you that "you can't get in right now, so please wait. When everyone before you leaves the queue it will be your turn." By capping the queue, and returning an error response (1017) back to your user you've invalidated the most fundamental function of the queuing system in the first place. This isn't rocket science...The Queue is still there, the Queue is just full. Login and Lobby servers do not have unlimited capacity and those, when the world is full, followed by the Login and lobby servers being full, it cant put you in Queue. There's no room for you to queue, so it had to kick you out. The Queue is working, it's just overloaded by everyone that is trying to long in before you. They need to make the line somewhere or everything goes down.
Last edited by ZhangoSqu; 09-02-2013 at 09:02 AM.
As I said, the login and lobby servers do not have unlimited capacity. They cant hold an infinite amount of people in the queue. Even they have their limits, you can't ask for the impossible.
Then they need to DRASTICALLY increase the queue load, because I have NEVER been over 200+ in a queue, it's generally always 100 or under and you get in within 30 seconds almost always when you do end u in the queue.He worded it wrong. The Queue is still there, the Queue is just full. Login and Lobby servers do not have unlimited capacity and those, when the world is full, followed by the Login and lobby servers being full, it cant put you in Queue. There's no room for you to queue, so it had to kick you out. The Queue is working, it's just overloaded by everyone that is trying to long in before you. They need to make the line somewhere or everything goes down.
Many mmo's have a queue system that handles THOUSANDS of people and can take 20+ minutes of waiting.
i cant even see the server list lol
Or they need to revisit their server infrastructure. I suspect that their lobby and login servers may be performing more than just the eponymous operations. Ideally you'd have one lobby server with a similar capacity to that of most social networks. Your login server (one for each world, and I'm ignoring the complexity of multiple nodes here) would be responsible for managing login requests, the queue, and passing a message back to the client to tell it that it is now connected to the game. That's it.Then they need to DRASTICALLY increase the queue load, because I have NEVER been over 200+ in a queue, it's generally always 100 or under and you get in within 30 seconds almost always when you do end u in the queue.
Many mmo's have a queue system that handles THOUSANDS of people and can take 20+ minutes of waiting.
sounds like the Release of FFXI the first time around.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.