My best guess is, this is a server synchronization issue.

Normally, the client should calls the server and wait for a callback. If the server response takes too long, a timeout will be issued on both the server and client. The server will drop the call, and the client will send a new call to the server.

What we likely have here is the server timeout being set longer than the client timeout. When the client gets timeout and sent the server a second request, the server is still processing the first, and now register two separate instances of the same client. This triggers the multiple account kick off.

When the connection between server and client is good, this bug is hidden, as timeout will not be reached. But when there is lag involved.. the bug shows up as a gamebreaker.

Oasis.. please get someone who understand server-client coding to deal with this bug. (Honestly, the most likely cause would be an extra 0 in the server code that set the timeout limit.)