Originally posted by [b]theultramage[/b]
http://www.eathena.ws/board/index.php?autocom=bugtracker&showbug=1281
In several places, the TXT login server modifies the stored login_id1 value to apparently prevent the client from auto-resuming after some account modification.
The mapserver also has a few places where this is done.
login server:
CODE
ARR_FIND( 0, AUTH_FIFO_SIZE, j, auth_fifo[j].account_id == account_id );
if( j < AUTH_FIFO_SIZE )
auth_fifo[j].login_id1++; // to avoid reconnection error when come back from map-server (char-server will ask again the authentication)
map server:
CODE
sd->login_id1++; // change identify, because if player come back in char within the 5 seconds, he can change its characters
// do same modify in login-server for the account, but no in char-server (it ask again login_id1 to login, and don't remember it)
None of these are present on the SQL login server, nor is there any trace of this in jAthena. It also doesn't seem to affect anything else, because the player is usually kicked and all auth data destroyed in the process.
I suggest re-evaluating the need for this thing.
This post has been edited by theultramage: Mar 27 2008, 03:38 AM