
got locked out twice, first time I managed to salvage it but now I'm permanently stuck in 3102.
I don't mind it really as this is a stress test, but it just shocks me how Square Enix really has no actual form of communication, nor have they bothered to reset servers. They rather just leave a decent % of testers stuck in 3102 than get them back in game to stress test more. Baffles me and this actually is my first beta test where the company test has made almost no effort to resolve log-in issues. Ontop of that the beta forums to report issues has been down for at least 50% of the test ; so exactly how are we even going to report issues?
Either Square Enix was seriously thrown for a loop by the amount of people testing and posting (how? They knew the numbers since August 2nd and had 2 weeks to plan... ) or they just flat out didn't do much of anything in that time and under-estimated almost everything.
Funny thing is, there is an easy fix for this problem that blows my mind why SE has not done this. It is called an AFK time out
you know... something most MMOs have had since ye olde days , just like the ability to hide/show quests 
It is what it is though; Guess we shall find out how good Square Enix is at dealing with server load come early access, and fixing problems like this.
PS: At least we got "Confirmation" about you know what from this error
That's right Gabe, we're onto you!
I don't mind it really as this is a stress test, but it just shocks me how Square Enix really has no actual form of communication, nor have they bothered to reset servers. They rather just leave a decent % of testers stuck in 3102 than get them back in game to stress test more. Baffles me and this actually is my first beta test where the company test has made almost no effort to resolve log-in issues. Ontop of that the beta forums to report issues has been down for at least 50% of the test ; so exactly how are we even going to report issues?
Either Square Enix was seriously thrown for a loop by the amount of people testing and posting (how? They knew the numbers since August 2nd and had 2 weeks to plan... ) or they just flat out didn't do much of anything in that time and under-estimated almost everything.
Funny thing is, there is an easy fix for this problem that blows my mind why SE has not done this. It is called an AFK time out


It is what it is though; Guess we shall find out how good Square Enix is at dealing with server load come early access, and fixing problems like this.
PS: At least we got "Confirmation" about you know what from this error
