The return of 3102

[Rekia]

I really hate myself for logging out right now. I was so excited that I finally got in, I thought the server problems were fixed so I wanted to switch characters and.... 3102.

[Dann]

People could try this.
Made a charicter on a JP server logged in.
Logged out.
Was then able to log in on an NA server.
Good Luck!

[Praesidium]

I got home from work one hour ago, logged in, my internet decided to shut down for some reason, try to log back in, one hour on error 3102 now.


WTF SE LOG ME OUT WHEN I FREAKING LOG IN THE LAUNCHER!

[ShinrinCole]

I think this is their new tactics so that it will not congested by server now. Its been 9 hours past and yet no resolution in this matter. This may be an intentional scheme to let other log-in :P

Check the the news on the front page, square is working on it.

Do people not care and check the main website at all to see updates on things?

[Tahldon]

Check the the news on the front page, square is working on it.

Do people not care and check the main website at all to see updates on things?

Lol. No. They are far too busy bristling with rage and conjuring a post on par with the flames of hell to do so.

Also, they hate your patience.

[Hvinire]

Hello everyone,

Since the conclusion of this morning's maintenance, the development team has addressed an issue causing the aforementioned 3102 error for many players. We are also now assisting the affected users and will follow-up once the process has been completed.

While we appreciate the assistance in providing your character names and Worlds, this information is not needed to resolve the issue. Thank you for your patience as we do our best to ensure everyone can log in and play.

[Hvinire]

The issue has been addressed for all affected players.

[Alhanelem]

I did get a 3102, but it cleared up after about half an hour. (Much longer than it should take, but at least it wasn't indefinite.) And it seems they've fixed it for others.

[DoctorPepper]

The issue has been addressed for all affected players.

No it has not, I'm still getting the error and have been for over 2 hours now.

[Chaneke]

They posted the fix 10 mins ago.. not 2 hours ago...