3102 from logging out normally.

I logged out normally through the games UI. I tried to log back in a few minutes later and am getting the 3102 still in game error.

I can understand getting this from a disconnect, but from logging out normally? Thats just total crap. This last maintenance seems to have brought along as many new problems as it supposedly fixed.

Same -10chars

Same thing. Logged on an old char in order to mail items to my new character, logged out and now I can't get back into the game on the other character.

I logged out using the correct method via the UI to go make some lunch and do some shopping. Now about an hour later it gives me the 3102 error. Does this mean we should just not log off ever and keep our characters online at all times thus blocking game access to other players? :( Something definitely appears amiss with this.

Oh well I haven't really been able to play much anyway with all the full servers and queues so I suppose I can get back to finishing my book before I have work.

Same here, normal logout in the city and now with all Characters Error 3102

Same here, logged out and 3102 now, all characters locked. Gogo square and Yoshi with "we fixed 90000 and 3102"

Same here 3102.

Same thing happened to me. Rebooted the client and was stuck on the start menu for a bit (the start option was greyed out) before I received the lobby full error and got kicked out.

same logged out via bed in inn.

I'm never logging out again. This is going to be like SAO.

This is also happening to me. I logged out using /logout and now I'm being hit with 3102 whenever I try to get back online.

Same issue other than i crashed while doing ifrit HM (My weapon dropped while i was gone after like 20 runs). Zeith Xilocient - RIP

Same deal here as well. Played a little bit this morn then logged off to take care of a few things only to find myself hit with 3102 still logged in error 2 hours later.

Same problem than Seldaris here :mad:

Normal log out = 3102 error? What's the deal SE? Glorious Maint.

I'm sure this issue will be addressed (not fixed) 10 days from now just like the server issues.