restore disconnectTimer, there are instances where a subsequent connection to the login server won't work because the client is still trying to use the previous (broken) session. We can't insta-disconnect since the response needs to go out to the client first and it needs to acknowledge the packet.
There will be a 1 second disconnectTimer, which means this login hang behavior can still happen (potentially on a really lagged connection or spamming password attempts). The likelihood however is largely reduced.
restore disconnectTimer, there are instances where a subsequent connection to the login server won't work because the client is still trying to use the previous (broken) session. We can't insta-disconnect since the response needs to go out to the client first and it needs to acknowledge the packet.
There will be a 1 second disconnectTimer, which means this login hang behavior can still happen (potentially on a really lagged connection or spamming password attempts). The likelihood however is largely reduced.
image
restore disconnectTimer, there are instances where a subsequent connection to the login server won't work because the client is still trying to use the previous (broken) session. We can't insta-disconnect since the response needs to go out to the client first and it needs to acknowledge the packet.
There will be a 1 second disconnectTimer, which means this login hang behavior can still happen (potentially on a really lagged connection or spamming password attempts). The likelihood however is largely reduced.