Punishment Configuration

punishments.yml controls violation expiration, staff alert cooldowns, and shared punishment actions.

What this file controls

Defaults include a 10,000 ms violation-expiration window and a 1,000 ms per-player/check alert cooldown. The cooldown limits repeated staff messages; violation accounting and mitigations continue on each fail.

Use the generated punishments.yml as the guide to the available action and tier format. Do not hand-edit its defaults-revision field; FairPlay manages that migration value.

Tune punishment timing without guessing tiers

  1. Back up the generated punishments.yml and review its action and tier entries before making a change.
  2. Compare the violation-expiration window and per-player/check alert cooldown with their 10,000 ms and 1,000 ms defaults.
  3. Change one timing value or tier at a time, then review the result in a controlled session. Leave the defaults-revision field unchanged.
  4. Record the changed values so staff can diagnose later behavior.

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