Warnings & Auto-Escalation

Give players a formal warning, and let the plugin step in once they go too far.

Warnings are a record. On their own they tell a player to stop. Combined with thresholds, they let PhantomBans take action automatically, so a repeat offender gets muted or banned without staff having to watch the count.

Warn a player

/warn <player> <reason>

The player is told they were warned and why. The warning is saved to their history.

Auto-escalation by threshold

You can tell PhantomBans to run commands automatically when a player reaches a set number of active warnings. This is set in the config under warn-thresholds.

warn-thresholds:
  5:
    - "mute {player} 1d Reached 5 active warnings"
  10:
    - "ban {player} 7d Reached 10 active warnings"
  15:
    - "ban {player} permanent Reached 15 active warnings"

The number is the warning count. Each line under it is a console command to run when the player hits that count. Use {player} for the player’s name. You can run more than one command per threshold.

Punishment ladders (templates)

For offences that should get worse each time, PhantomBans has templates in templates.yml. A template is a ladder of steps for one offence. The first time a player breaks that rule they get step one, the next time step two, and so on. You apply a template from the punish menu.

This is great for rules where the punishment should grow: a warning, then a short mute, then a ban.