Errors Galore! :D

[sschafi1]

Been trying to login for quite a while now. Then I got queued, and thought "Oh, cool. I can actually play in a few!" While I was in said queue, out popped Error 1017. Go figure. Repeat ad infinitum.

Then I actually got into the game, and got 90000'd. Got in again, and received 10102. Then the JP servers were down, but since I play on Cactuar, I could still try and spam my way in. Nope. When I got to the lobby, Error 2002 reared its head.

And now the NA/EU server list is down.

Isn't this wonderful? I'm so glad I payed for this experience.

[RebbecaNakayama]

got on today hoping to play it was around 4pm and kept getting 1017 then 2002 and then the NA/EU servers went down so waited until they fixed it "all right I get to play" I signed in and got 2002 then signed in again and got 1017 a couple of times and now it's saying NA/EU servers are down again XD I wants to splores D: but I'll be alright

[Ophis]

Ironically I play on the JP server and now the JP server list is down. Isn't this game just wonderful?

[Nullsleep]

It's this login dungeon... it's too broken... I mean I've googled for a while now trying to find a decent strategy to beat it but it's just not been written. First you have to defeat the 2002 monster, then you have to get past the "Unable to retrieve JP/NA/EU server list" mid boss, then you have either the 3102 or the 1017 boss ( whichever decides to spawn ). If you're lucky enough you get the epic rare relic item "You can finally play the game" and pray you don't run into the 90k NM. Seriously SE nerf the login dungeon it's overpowered in epic proportions.

amirite guys?

[wizisi2k]

pity I can't use my FFX save to defeat these 3 monsters. That would make these bosses a walk in the park unless they are also crazy stat bosses. My MRD 26 can't login but I decided to try adapting a policy that worked during 1.0 beta: wait 3 min between attempts-it has worked for me even if it took a few times

[sschafi1]

I got a brand spanking new error earlier today! (Well, new for me anyway). Error 6002. I guess it was 2002's 2nd cousin.