Repository navigation
Fix SetEnabled method to set enabled state correctly - #267
Merged
Merged
Conversation
Removed the default enabling of automatic banning in the anticheat system.
Collaborator
Author
|
Sorry, was a little too quick with this and missed it. :( |
Hucaru
approved these changes
Mar 30, 2026
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.
This pull request makes a small but important fix to the
SetEnabledmethod in theAntiCheatsystem. The change ensures that the method correctly sets theenabledstate based on the provided argument, rather than always enabling it.SetEnabledmethod inanticheat/anticheat.goto assign theenabledfield based on theenabledparameter, instead of always setting it totrue.