Post: #3

(07-19-2013 04:48 AM)RanXerox Wrote:  In the example above, the log entries are composed as follows:

HOUR:MINUTE:SOCKET:MESSAGE

So here is a possible explanation line by line in English:

Code:

23:45:144:Client connected [Total:1] ('127.0.0.1' 1/1)..... A client connects to the server on socket 144
23:45:144:Login 'a'                                         The client on socket 144 logs into account 'a'
23:45:140:Client connected [Total:2] ('127.0.0.1' 1/2)      Another client connects to the server on socket 140
23:45:140:Login 'a'                                         The client on socket 140 logs into account 'a'
23:45:144:Client disconnected [Total:1] ('127.0.0.1' 0/1)   The client on socket 144 disconnects from server (and account 'a')
23:45:140:Setup_Start acct='a', char='rome'                 The client on socket 140 creates a character
23:45:ERROR:140:Bad Login 2                                 The client on socket 140 fails to login twice...
23:45:ERROR:140:Bad Login 0                                 ...because account 'a' was just disconnected
23:45:140:Client disconnected [Total:0] ('127.0.0.1' 0/0)   The client on socket 140 disconnects from server

The solution is to wait a bit longer after you log out (or close a client) before logging in again.

Hello,first,thanks for your info,but the solution dont run,the problem is only with pleveled accs,i think there is a rare script or wathever blocking accounts with special plevel.
If i get plevel on my acc,and relog,account blocked,char deleted,if i close the client,same,and if i log out,and try to login next day,the same.
Is very rare...