Closed themuntdregger closed 10 years ago
Fixed
On closing socket, the char id on the client node was not being cleared to zero. Hence, when char logged back on, the char id on the previous client node would cause the connection to appear concurrent.
Fixed
On closing socket, the char id on the client node was not being cleared to zero. Hence, when char logged back on, the char id on the previous client node would cause the connection to appear concurrent.