Skip to content

Add world-level autoBan config to globally toggle autoban - #265

Merged
ErwinsExpertise merged 10 commits into
Hucaru:masterfrom
ErwinsExpertise:master
Mar 27, 2026
Merged

ErwinsExpertise merged 10 commits into
Hucaru:masterfrom
ErwinsExpertise:master

Conversation

@ErwinsExpertise

Copy link
Copy Markdown
Collaborator

This pull request adds a configurable setting to enable or disable the automatic banning (auto-ban) feature in the anti-cheat system. The change introduces a new autoBan flag that can be set via configuration files and is propagated through the server, allowing runtime control over whether anti-cheat violations result in automatic bans. When auto-ban is disabled, violation tracking becomes a no-op and no bans are issued automatically.

Anti-Cheat System Enhancements:

  • Added an enabled atomic boolean field to the AntiCheat struct and a SetEnabled method to allow enabling or disabling auto-ban at runtime. All violation logging methods now check this flag before proceeding. [1] [2] [3] [4]

Configuration and Propagation:

  • Introduced the autoBan configuration option in both config_dev.toml and config_world.toml, with a default value set to true in the code. [1] [2] [3] [4]
  • Extended the World struct and related serializable data to include the AutoBan flag, and ensured this flag is set from configuration during world server initialization. [1] [2]

Channel/World Communication:

  • Modified the channel registration handshake so that the world server sends the AutoBan flag to the channel server, and the channel server applies it to its anti-cheat system. The channel server now logs the status of the auto-ban feature at registration. [1] [2] [3]

Comment thread anticheat/anticheat.go Outdated
@ErwinsExpertise
ErwinsExpertise requested a review from Hucaru March 27, 2026 16:04
@ErwinsExpertise
ErwinsExpertise merged commit a86b204 into Hucaru:master Mar 27, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants