Quote Originally Posted by Tsobail_InKari View Post
Add an AFK Timer and most of the issues will be gone. Also Add a login queue of at least 1000 players possible and every single issue will be removed. I dislike the 1017 error, but if Every time I logged in I got a login queue I at least have an Idea of how long it will take.

I can alt-tab and do other things while waiting for it to finish (obviously having sound on while out of window so you will hear it log you in).

To indicate that you are going to leave before they attempt to implement a singular fix is short sighted. Honestly IMO going the new server route is short sighted and takes to long to implement. They didn't have new servers sitting around, and had to place an emergency order with whoever they use (Dell, HP, IBM... or what ever company). And those take time, Also most likely each server is not a single server, but a cluster of multiple for load balancing and the like. I remember reading in the future patch notes that there will be updates done to the server as well, but SE hasn't indicated what those are going to be for. (tried to look for the note but can't find it now like a goober)

Ultimately, To leave at this point is to soon. At least wait for the "fix" to see if it works, I just hope they open up character makes on Exodus soon so my wife can make a character on my server and I can finally start leveling my main class.

I'll chime in a little here.

Login queue: from what I've seen and can assume from the workings of the game so far, the login queue (handling you logging in, making a toon, and pulling a server list) is completely separate from the server. All server related functions (from requesting to log in, all the way to playing) are handled on another cluster. So all the login server really does is query the game server and receives this 1017 error. It cannot generate a queue because the login server has no idea when an opening occurs or even what capacity the server is running at. Shoddy coding to say the least, but this seems to be the way they coded their servers to work together.

New servers: not as hard as you'd think to implement. Most likely they have backup images of all types of game servers (login, servers, dungeon). This allows them to quickly repair a damaged or corrupted server, and in this case allows them to quickly take a server out of the box, image it, and force it into a cluster. They're also likely using virtual clustering and virtual servers, which allows them to take say 5 servers and virtually shard that cluster into 20 servers, or whatever numbers you'd like to use. That makes the baseline imaging of a new machine even easier given that the existing cluster can shift the virtual machines around as needed (or manually) to balance the load.

The "fix" here is simply that to add new hardware, usually you cannot have users online because a lot of these programs go crazy when hardware starts changing up (like plugging a new IDE drive into your computer while it is running in windows). So they schedule more than enough time to implement the changes start to finish (which is more guess work than actual science) and then go for it. The reason they chose Wednesday was to give themselves some prep time and to not disrupt the game during a US holiday. They understand a lot of people are put off by the fact that they cannot log in, but many more are enjoying their experience, and they don't want to close the doors on a big holiday. Imagine the backlash of that... like Battle.net's error 37 but over a 3-4 day weekend. It'd be the end of the world, at least on the internet.

Anyways, one more day. Good luck sweating it out! I hear exercise is a heck of a drug, try it or religion to ease your withdraw symptoms.