-
Random d/c into 3001
So I was just out mining, minding my own business, when I'm 90k'd off.
Sighing, I reconnect to find out what kind of monstrous queue awaits me and all I get is:
"The world is currently full. Please wait until an opening is available and try again."
Like.............. that's what a queue is for. Am I just supposed to know when that is?
Guys I get it.. there are server capacity problems you weren't able to solve ahead of EW's launch. But we're going on a week of this now. It's getting real old, real fast if you know what I'm saying.
-
In queue. DC'd. 3001. BS.
-
Same here, waited all morning, reached place 28 in the queue -> 3001.
Haven't been able to join the queue at all since.
Some hardware must have just fell over if we all got 3001 at the same time...I see Xeno is Cactuar as well.
Imagine if software sales had to adhere to the same consumer protection laws as TVs.
-
+1
I am completely unable to even queue up for Cactuar because of 3001 errors. Is there going to be a maintenance to fix these 3001 errors?
-
Yep, I've got the same problem on Cactuar. Was in queue for about 2 hours, got a loading screen as if it was logging in.
Then I'm hit with some 10k error and booted to the title screen.
Now every time I try to rejoin the queue, I get a 3001 error.
Was able to create a new character on one of the JP servers, and logged in with out any problems (no queue at all).
-
Primal-Ultros here. 3001 as well. I also noticed that NA in general is blocked off completely for character creation atm. Hopefully, some communication comes down the line soon
https://na.finalfantasyxiv.com/lodestone/worldstatus/
-
Same thing on Gilgamesh. Cannot join the queue. 3001 error.
-
I've made it into Q now but I have been stuck a 673 for over 30 minutes. Which was also my starting position when I was able to queue.
-
was in game. 90002 error. 3001 trying to rejoin in midgardsormr
-
Got through the Que... then got slapped with the 3001 error... Not even letting me get back in que no Leviathan...