Continuously check for changes to in-game players ban status with a bulk request#86
Open
zeb-kolb wants to merge 12 commits intotovyblox:masterfrom
Open
Continuously check for changes to in-game players ban status with a bulk request#86zeb-kolb wants to merge 12 commits intotovyblox:masterfrom
zeb-kolb wants to merge 12 commits intotovyblox:masterfrom
Conversation
Checks for recent changes to the ban db with a bulk request and kicks out any players that were banned after joining a server.
Author
Contributor
|
lgtm |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Automatically kicks a player from the game server immediately after they're banned through the Tovy instance. Keeps a log of newly banned players on the instance that the game server requests at a specified rate.
The default check rate is 5 seconds, but in a similar system that I use for my groups, the server can easily handle a check rate of 1 second.