Stoatmod / Cases and warning policy

Warnings and moderation cases

Warnings contribute to escalation while cases preserve the server-scoped record. Removing a record and reversing a punishment are not the same operation.

All documentation

The details, in one place.

Create, inspect and remove Stoatmod warnings and understand how cases interact with escalation and appeals.

  • Reviewed 31 August 2026
  • 4 sections
  • Documentation

Default escalation

The default policy applies a timeout at three active warnings, a kick at five and a ban at seven. The dashboard can replace this with a staged policy using unique thresholds.

~policy show

Review the current warning policy.

~policy set 3 5 7

Set timeout, kick and ban counts.

~policy reset

Restore the default policy.

Create and inspect records

~warn USER_ID REASON

Create a warning for a valid Stoat user ID.

~warnings USER_ID

List active warnings.

~case CASE_ID

Inspect one case.

~cases USER_ID

List recent cases.

Removal and reversal

Removing a warning case stops it contributing to warning escalation while retaining its removed state. Removing a non-warning case does not undo a timeout, kick or ban. Use the appeal or appropriate moderation command when the real server state must change.

Record quality

  • Copy a valid member ID.
  • Write a reason that another moderator can understand.
  • Add notes when a later manual correction changes the outcome.
  • Never assume every operational event creates a case or contains actor attribution.

Continue the task

Related Stoatmod resources

Moderation cases and review historyOpen resource →Review and resolve appealsOpen resource →Mute, kick and ban actionsOpen resource →

Ready to configure a server?

Install Stoatmod, then verify the first outcome.

Open the official bot profile →