"This account is already in use"
 

Sometimes reconnecting results in said error("This account is already in use"). Apparently sometimes when you reconnect your player isn't disconnected... thus your account is stuck connected and has to wait to idle out or have a staff disconnect it before you can reconnect again.

That happens to me sometimes too.

Happens to me but I haven't had it in a while.

That's really odd when it happens.
I always thought it was an issue with graal and its process. Last time I experienced this, I closed all processes related to Graal and opened some random RC, my ingame character was still here, but nobody could see it in the map. It dissepeared after some minutes.

This happens to me alot, but when I click "Login" again it works.

It's quite simple actually. I learned this from another game also known as Runescape. Graal does not physically have a logout function, so in Runescape if you didn't logout properly your avatar would stay in the game for 2 or 3 minutes before it disconnected it's self. So while you were waiting to login your player was still in the game. This seems to happen with Graal too, since we don't have a logout function when we leave our player stay on the server for a limited amount of time. You may or may not be seen on the server, but thats besides the point. So basically if you just wait a little bit it should log you off because you get disconnected for no playing activity. Thats just my observation I am not saying its true.

You usually get disconnected for idling (if enabled) after 25 minutes or so, that's not a little bit

ESC key logs you out.

It's not 25 minutes, its more like 10. However, I have noticed it only takes like 2 seconds, it will say "that account is currently in use" I try again about 10 seconds later and it allows me to get back in.

I'm pretty sure that if you log into the same server using two different clients, the second client will kick the first off. It doesn't do the same when your player has lagged out and it probably should.

It's all related to the client pinging the server and vice versa. If your connection gets abrubtley terminated, the server might not recognize that the player has left and wont disconnect it until a few failed pings are returned.

Can't say I've had a problem like this ever, so it's quite surprising to me to see how many people are saying "This happens to me too, sometimes". If it's something with reconnecting, perhaps it's serverWarp() initiating too quickly and not giving the client a chance to send the "I've logged out" data for a server to receive. Not sure about the other things mentioned that have presented this problem though and Ziro's idea is likely on the money for the "lagged out" one, and I could be wrong about the above as it is.

It wasn't a scripted reconnect. It's going to the serverlist and trying to reconnect to the server.

Never happened to me when I do that..

Graal doesn't let the second client kick the first client until I think at least one minute has passed since the first client has been logged in. - Also it usually takes about 1-3 minutes before the first client disconnects from a bad logout (like say your internet is pulled)