Mitigation Configuration

mitigations.yml contains per-check mitigation controls, reach compensation, and separate kick and ban settings.

What this file controls

Automatic kick and ban are separate controls and both default to disabled. Their allowlists are separate from other mitigation actions.

increaseReach is a bounded air-swing compensation opportunity for a qualifying clean beneficiary against a target. It does not give extra reach to an offender or permanently change a player’s reach.

Review the generated file before changing policy so you can see which mitigation gates are enabled on your server.

Change one mitigation gate at a time

  1. Back up mitigations.yml and identify whether you are changing a per-check group, increaseReach, totem/Elytra/macro-spear controls, or the separate kick/ban gates.
  2. Check the current kick and ban values; both controls default to disabled and use separate allowlists.
  3. Treat increaseReach as compensation for a qualifying clean beneficiary, not extra reach for an offender.
  4. Change one gate at a time and record the new value for staff review.

Apply and verify changes

After editing a setting, use the reload command when that setting supports reload. If the change does not take effect, check the configuration troubleshooting guide for the setting’s restart requirements.

Browse all documentation