Response from SE regarding Error 3102?

[Roelon]

I'm simply asking - have the developers / admins / whomever acknowledged or made any sort of comments regarding the post-downtime (03 SEP) issue regarding the "still logged in" error?

I've done a search of the news, topics, and dev posts, but haven't come across anything.

Please, this is not the thread to trash devs, impress ignorant opinions, or list your server and character name in a roster amongst those affected. Please keep replies structured, informed, and constructive.

In the interest of being constructive, I'd like to know more about how those who are affected logged out.

E.G.: I played immediately after DT. I played for about an hour or two. I was in a non-sanctuary area, and decided to quit. I selected the logout option, then Alt+F4 simply because I didn't want to wait for the 20-second timer to expire. I selected the "exit game" option. A few hours later, I cannot log back in; error 3102.

Why am I posting in such a manner?: I have a background in IT, experience in QA . A "Bug Report" manner of posting about a problem would likely be more effective to Devs when addressing the problem. I'd like to know if it's a fluke / random / etc., or if it affects others who logged out in the same manner (therefore narrowing down the problem)

[teknotaz]

there has been no news yet on it. the servers will probably be taken down again to fix this new problem

[Pimsley]

You can expect this response from SE:

We apologize for any inconvenience this may cause and thank you for your cooperation and understanding.

[Hellborn]

Don't expect SE to come out and say anything, they have piss poor CS. Yesterday I waited for live chat for 2 hours only to be told, at the end of the queue, that there was no representative available at the time and to try again later.
As for the 3102, it affects people logging out of the game, period, no matter HOW you log out, you get stuck.
I put up with the launch crap until now, but honestly, I am losing faith in them now. I want this game to be a success, and it saddens me to see how badly it is handled.

[Azazello]

Yoshi-P already commented on 3102, back on August 21:

Regarding the Error 3102 Issue
Again, we would like to apologize for our delay with the update on Error 3201 issue.

The issue has been resolved after the maintenance that was performed during the Beta Test and we have confirmed that the issue has been fully addressed.

We have corrected the character data for all the characters that were affected by this error, and you'll be able to participate in both Early Access and the official service without any problem.

Once again, for those who were affected by this issue, we deeply apologize for the inconvenience and ask for your support in both Early Access and the official launch of the service.

Emphasis mine.

Hey ... somebody had to do it.

Kweh!

[Ratm3000]

It is not just the 3102 error, it's has been the constant 90k error. Massive lag in the game for some people that they need to fix as well. Where the receive and send go down to 0 and then spike up, constant boots and 3102 followed.

[Roelon]

Thanks - but only Teknotaz and Azazello have offered any constructive information about the issue.

I get it, frustration will make you want to vent. Don't do it here. This is not the thread.

[Goggo]

I logged from home two hours ago to check if it was working alredy, everything was fine so I logged out.

I came back, tried to log in and this error popped.

[Roelon]

Interesting - I was just able to log in. Not sure why.

Also, it should be noted that I was seeking a party in the Duty Finder when I logged out. Not sure if that was a cause, but every bit of information surrounding the circumstance of the failure should be noted.

[okunoin]

I went to my inn, went to sleep in the bed and selected the 'log out' option, went to character screen and everything. I still got the 3102 error when I returned to the game. It sounds to me like some kind of syncing error between the player and servers at SE.