Server is full. 3001 Error

[VorpalSpork]

Okay, so Friday I was getting the 2002 error and unable to play, now I try and join the queue and I get this "This World is currently full." 3001

A couple of times I've actually made it into the queue, but am quickly booted out with this 3001 error.

Isn't the point of the queue for getting in when the world is full? This is getting a bit ridiculous.

[goforfink]

Have been getting this as well. Driving me slowly into madness. I hope they refund the people who paid for early access and can't even get into the queue, let alone the actual game or the new content.

[BaadF00d]

Tend to agree, on friday the Queue on tonberry was over 11000, now when its not giving an error 3001 the queue is quite small between 50 and 1000. But it matters naught as a queue update results in a drop from queue, and an endless cycle of 3001 errors.
I guess just to many people want to play. I noticed you can use the Visit alternate world feature to try an avoid the queue, but it doesnt work, I can create characters on garuda, and play them but cant visit garuda without getting the same error 3001.

[vellaude]

World visit system somehow doesn't work for me. Tonberry is full so I tried to transfer to another world server, but it kept sending me back to tonberry even though it said world visit transfer is succesful, and got 3001 error. It's just and endless loop of not being able to login.

[Phetza]

Im pretty sure now that most people here have Tonberry as Homeworld and only Tonberry people have this problem, i have friends from another server who can log in to theirs own home world just fine like ramuh and kujata with 100+que, i guess its prioritize people to log in to their homeworld first then the visitor.

This is not good at all, im pretty sure people in other zone like NA have more population than JP or in elemental and no such a problem like this one , and i thought 10000 que was bad but cant que at all is worst.

[vellaude]

Im pretty sure now that most people here have Tonberry as Homeworld and only Tonberry people have this problem, i have friends from another server who can log in to theirs own home world just fine like ramuh and kujata with 100+que, i guess its prioritize people to log in to their homeworld first then the visitor.

This is not good at all, im pretty sure people in other zone like NA have more population than JP or in elemental and no such a problem like this one , and i thought 10000 que was bad but cant que at all is worst.

I think so too. People said they can log in just fine from their non-tonberry character. I wonder if this is because I logged out in other server and my character just got stuck and not being able to log in.

This is so frustating I've been trying for hours to log in and still not being able to get into the game. Is there a way to reset my character's world location so she got back to tonberry without logging into the game..

[VorpalSpork]

I'm definitely Tonberry, but even if I change worlds I get 3001 error.

[Nasriel]

Fellow Tonberry player here. I logged in at approx 12pm and the queue was at about 50 so I got in after a few minutes. I logged out and attempted to get straight back in at 5:30pm and got Error 3001. It is now 9pm and I am still getting error 3001. Like everyone else the visit another world feature just gives me the exact same error. I got into a queue at one stage for Unicorn which was at 174 but after a few minutes and it dropping down to 99 I got booted from the queue with Error 3001.

[VorpalSpork]

In their status update, they don't even acknowledge the 3001 error, which I find incredibly frustrating. I haven't been able to play at all.

[Drakenz]

same here for me. my main character is still offworld(Tonberry is my homeworld). Every login since 6 hours ago gives me the 3001 error. i have switched worlds from Aegis to Ramuh to Unicorn but every world gives the same 3001 error.

Please help me. I don't know what's wrong. My FC members seem to be able to login after a while but not me. There is no queue. it straightaway goes to 3001 error. Very frustrating.