Stoatmod / Moderation / Moderation cases

Moderation cases.

Bring the action, reason and follow-up into one server-scoped record. Find a member’s history, add context and give your team a clear starting point for review.

All features

Keep the reason with the decision.

Keep reasons, evidence and follow-up connected to the decisions your team makes.

Learn the case review flow
  • Records: Reasons · Notes · Evidence
  • Scope: Your server
  • Find by: Case ID or member

The walkthrough

How it works.

From your settings to the result your team can review.

  1. 01

    Take an action

    A warning or eligible moderation action creates a server-scoped case.

  2. 02

    Keep the context

    Review the reason, action and available evidence; add follow-up notes.

  3. 03

    Make the next decision

    Review the member’s history, remove a case or handle an eligible appeal.

01

What belongs in a case

Warnings and eligible moderation actions can create a case, with notes and appeals connected to the record. Routine link deletions and general operational events may appear only in event history. Actions taken outside Stoatmod may not identify the acting moderator.

  • Warnings and manual mutes.
  • Spam or policy timeouts and bans.
  • Stoatmod-initiated kicks and manual bans.
  • Appeals, moderator notes and supported evidence attachments.
02

Make the reason part of the action

Moderation commands require a reason. For mutes, put the duration before or after the reason; leaving it out uses one hour. The examples below use a placeholder USER_ID—replace it with a member’s ID or mention.

~warn USER_ID repeated spam

Add a warning with a reason.

~mute USER_ID 25m repeated spam

Mute for 25 minutes. You can also write the reason before 25m.

~unmute USER_ID resolved after review

Remove a timeout and record the reason.

~ban USER_ID repeated harassment

Ban a member with a reason.

~unban USER_ID appeal accepted

Unban a member and record the reason for reversal.

03

Warning and removal behaviour

The default warning ladder acts at three, five and seven active warnings: timeout, kick and ban. A server can replace this with staged dashboard policy. Removing a warning case stops it counting while retaining the case as removed. Removing a non-warning case does not undo its punishment.

~case CASE_ID

Open one case.

~cases USER_ID

List recent cases for a member.

~remove CASE_ID

Remove a case from active warning counting where eligible.

04

Follow through on a decision

  • Check the member’s timeout, role or server state after an action.
  • Resolve delivery errors or missing permissions before considering the action complete.
  • Use notes to explain a later correction.
  • Review appeals separately from case removal.

Make it part of your server

Your community.
Your configuration.

Add Stoatmod Learn the case review flow →