Skip to main content
Warnings are the paper trail that makes later punishments defensible. On their own they do nothing except get recorded — the value comes from thresholds, which turn accumulated warnings into automatic action.

Warning someone

Requires Manage Messages. Creates a case, DMs the member (unless silenced with -s), and checks whether they’ve crossed a threshold.

Thresholds

Requires Administrator. When a member reaches that many warnings, the action fires automatically.
Aliases for the group: punish, punishment, action. warn threshold list only needs Manage Messages, so moderators can see the ladder without being able to change it.
Thresholds fire on the exact count. A threshold at 5 fires on the fifth warning and not again on the sixth — so a ladder wants a rung at every count you care about. There’s no “5 or more” behaviour.

Reviewing warnings

Warnings are cases, so the history commands cover them:

Resetting

Requires Administrator. Aliases: clear, wipe. Resetting clears their warning count, which means the threshold ladder starts over. The underlying cases stay in the history — use !history clear @someone to remove those as well.
!warn reset with no member resets the entire server. There’s no undo.

Designing a ladder

Forgiving, with a long runway before anything permanent:
Faster, because you have volume and can’t hand-review everything:
Jail before ban gives people a chance to explain themselves without you having to monitor DMs:
Needs !setup run first. Point them at the jail channel in the message:
Reason templates make warns fast and consistent. Save the reasons your staff type constantly, then use the template name:
!reason list shows them all.

Command reference