Simple math would of solved all your problems

Quote:

---

Originally Posted by Aaerie

It could of been a typo on their part and meant NA/EU. Regardless, here is the same thing from the "An Apology to Our Players Using NA/EU Data Centers". http://forum.square-enix.com/ffxiv/threads/68427

Although we have successfully addressed a number of serious issues in the past several days, we have nevertheless decided to implement login restrictions for the time being due to the extremely heavy load being placed upon the servers. In this way, we can ensure that the maximum number of players can play the game without risking a server crash. I know no one wants to wait to log in, but I hope you all understand why we believe this precaution is necessary.

FYI, I'm not a dude.

---

yeah could have been a typo. But if it wasn't, I really read it quite differently. Extremely Heavy Load on servers can literally be anything, even a loop that hasn't closed properly can run CPUs forever, and if you have 10 clients on a 50 client capacity server running the same loop you have x% more load than you should on a server.

Also Login Restrictions was the key word for me, as they also said maximum number of players without risking a server crash. I interpreted it as the login in requests were putting more load on the servers than it should causing instability. They still have a max capacity on the server, but the login restrictions is the filter our clients are hitting when we see the 1017 "full server" when the server isn't full at all. but that is my guess.

IMO If the servers were actually full, we would be in a que without the login restrictions.

Quote:

---

Originally Posted by WingsofWar

IMO If the servers were actually full, we would be in a que without the login restrictions.

---

Yeah, and that is what is irritating me, and likely many people. It's not the wait, it's that you can't queue up and go get a sandwich or something, but you have to either not play or repeatedly try to login. It's a bit more than just a wait.

Possible solution: pretend like the launch is a month from now. By then half the subs will have left because of this and everything will be just fine! Maybe.

Quote:

---

Originally Posted by Szalvias

Yeah, and that is what is irritating me, and likely many people. It's not the wait, it's that you can't queue up and go get a sandwich or something, but you have to either not play or repeatedly try to login. It's a bit more than just a wait.

Possible solution: pretend like the launch is a month from now. By then half the subs will have left because of this and everything will be just fine! Maybe.

---

exactly, that is kinda whats been leading me to believe that the 1017 error everyone is seeing is actually just a filter, and doesn't correspond with the server being full at all.

and only a very small randomized number of players that attempt to log in actually gets into the request tunnel, in which is a line of X amount of players, which ends up in a que. So spamming 1017s is not doing anything against the server since your not really logging in, rather just returning tons of false alerts.

Its frustrating, a Que would be a nicer screen than having to hit the start button over and over again and getting people to not log out once in. This is why I'm baffled that they couldn't do the math and foresee this. Not even foresee ...but considered it as a possibility of something that could go wrong 'should' it happen.

I mean we are in 2013, load balancing servers in this day an age is possible and should not take this long. Not to mention it should of been part of their plan from day one.