What does the plugin do?
AAC protects your server from gamebreaking hacks and unfair advantages such as:
- Kill-aura (attacks players/entities for you, huge combat advantage)
- Reach (increases reach of hacker beyond fair vanilla reach of 3 blocks)
- Fly (allows players to fly in survival, potentially at speed that will crash your server)
- Other unfair advantages that harm your legitamate playerbase
Advanced Anti-Cheat is very user configurable, and as a result of this, is highly sensitive. Using the default configuration will result in false positives and is not recommended to be deployed in a production environment!
Install AAC by dragging it into your plugin folder, and restart your server.
Edit the config YAML to configure your commands to execute at a specific violation level.
It's best practice to have a test server (even a local one if getting a hosted one isn't an option) to test your anti-cheat configuration before deploying
Here is an example snippet of AAC's config:
So what do all the numbers mean?
A "check" in an anticheat is a part of the plugin that analyzes if the player is cheating or not, or if they are displaying suspiscious interactions/behavior. In AAC, each seperate check in the config.yml can be individually configured, the above "fastbow" check being an example.
lenience: 200is one of the "check-specific" configuration options, every check may have a different value that you can modify which specifically pertains to that check
The decay section of every check determines how much "VLs" or violation levels will go down (ms)
interval: 100means every 100 ms, the violation level of a player will go down by the amount
delay: 100how long to delay the decay of the violation level
amount: 1how much the violation level decays
The thresholds section is pretty simple, it just determines what commands should be run when a player/potential-hacker reaches a certain violation level (VL)
- See Conditional Commands for info on reducing lag related kicks/bans
- See AAC Optimization Guide for a detailed and advanced explaination of what conditional commands are
Many server owners use Celebrimbor's optimized config, which costs an additional $14. This configuration consists of numerous optimized changes that Celebrimbor has made over the years, and it is highly recommended to get it as a base for you to use with AAC on your server.
There's a false positive, what do I do?
No worries, AAC's configurability means that false positives are easily fixed. There are two types of false positives:
- Plugin related false positives: report to AAC Github Issue Tracker so the developer can fix it
- Configuration related false positives: false positives that you can fix
Fixing config related false positives:
- First, collect some information on the false positive, like what might cause it and some verbose data
- To collect verbose data, do /aac verbose and reproduce the false positive, or look in your AAC's plugin log folder
- The verbose data will show what part of the check is causing the false positive, you can specifically focus on that part in AAC's config.yml, go to the config
- Check your config values, perhaps add more leniency? Perhaps increase the violation level decay? Perhaps use conditional commands?
- If the above three don't work, there are always people in Bloom.host's discord willing to help you out!
Advanced Anti-Cheat is very user configurable, and as a result of this, is highly sensitive. Using the default configuration will result in false positives and is not recommended to be deployed in a production environment! READ THE SPIGOT PAGE BEFORE PURCHASING!