Character Creation Limitation (Aug. 24)
Just a heads up to those who didn't get in, that it may be hard from here on out.
|
|
|
|
|
|||||||||||||||||||||||||||||||||||||||||||||||
Character Creation Limitation (Aug. 24)
Just a heads up to those who didn't get in, that it may be hard from here on out.
The quote.
"Hello, this is FINAL FANTASY XIV: A Realm Reborn Producer and Director, Yoshida.
The maximum expected population limit is nearing for each World, and unless the current World simultaneous connection amount decreases, we are unable to open release the limitation.
In case we do release the limitation, there is a high chance that the corresponding World will crash or cause issues, and we are thinking that it will be difficult for us to release it for a while. We please ask you to consider playing in a World that has a low limitation.
We are sorry for any inconvenience that this may cause and ask to continue with your cooperation."
The maximum expected population limit is nearing for each World, and unless the current World simultaneous connection amount decreases, we are unable to open release the limitation.
That's the key problem right there, I found that out earlier today. Its not an issue of having too many characters created, its having too many characters playing at the same time. They're concerned about zone crashes due to high population, etc.
Its not uncommon for a new game to throttle connection during their initial start to avoid overpopulation of start zones, but it does seem like its unusually strict for this game. Its a shame that they chose not to go with "zone channels", they have the instancing technology already configured into the back-end. >.>
As of 0130 EST, friend of mine was able to create a new character on Excalibur, just a heads up for anyone who's still trying to get in...
Yep, we had a few get in today. It is painful if you do not get in during the first hour or so, but it will calm down as time goes on. Particularly when people go back to work on Monday, and late at night USA time.
I think we have almost eveyone now, thankfully.
Is this error 10102 I keep getting when trying to log in part of tihs? Or is something else going on...
I'm getting the same thing - can't log in. I was hoping everything would be fixed when I got us this morning . . . :(
If you hit errors, check the Launcher for news updates. They will put an announcement there if they are having issues or any maintenance. If you check it now, you will notice that they had login issues and had another emergency maintenance this morning to try and fix them.
If you do not see anything on the Launcher, put in a support ticket. If you want to post on their forums, go ahead, but make sure that is not your only report to them. Support tickets allow them to officially track issues and pass on to the developers. Forums are... messier, more difficult to organize and track and not as reliable. (trolls get involved in the threads)
edit: alternately, you can check the Lodestone, the same news links will be mirrored there, as well.
Well, as some know I managed to get my toon onto Excalibur. I hope SE fixes the queue though as I get on before work this morning (just now) and it flat out won't let me in due to the world being full (error 1017).
I think it is telling me to have breakfast and not play :P
EDIT: Upon checking posts on the official forum, I noticed that most servers (NA/EU data center) are having the issue.
It's rather unfortunate that we're not able to make characters on Excalibur at this time. I was trying to get a friend on with no luck, so we went to another server (Siren) to play. I'm enjoying the Arcanist class more than I thought I would. I'm going to try and split my playing time between the 2 servers until they can get this train wreck fixed.
They've been having login problems and bringing servers up and down, then they limit the flow of logins for several hours after maintenance. Like any other error message, its hard to tell when something is broken and when they are intentionally throttling player logins, we see the same error codes no matter what.
Its understandable for an Open Beta, but this is supposed to be a "release state" Early Access period and even I am starting to get frustrated with them. >_>
