cooldown_on_force_exit #2638
Merged
cooldown_on_force_exit #2638
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
really big update!🔥🔥👨🚒 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TL;DR
Added a delay when handling disconnects for clients that didn't properly logout.
What changed?
Modified the disconnect event handler in the ZoneServer2016 class to check if a client has properly logged out before deleting it. If the client did not properly logout, the deletion is now delayed by 10 seconds using setTimeout.
How to test?
Why make this change?
This change helps handle unexpected disconnections more gracefully by giving the system time to potentially recover or complete any pending operations before removing the client. This can prevent data loss or inconsistent states that might occur when a client disconnects abruptly without going through the proper logout procedure.