Moderation - Cases and Evidence
Every moderation action creates a case: a numbered record of the action, the member, the moderator, the reason, the duration (for timeouts, mutes and timed bans) and the infraction points it added. Case numbers count up per server (#1, #2, ...).
What creates a case
- Every moderation command (
/warn,/timeout,/untimeout,/mute,/unmute,/kick,/ban,/softban,/forceban,/unban,/note), and one case per user for the mass commands. - Actions taken directly in Discord. When someone bans, unbans, kicks or times out a member through Discord's own menus, the bot records a case with that person as the moderator and the reason they gave in Discord. Removing a timeout in Discord is not recorded as a case, but it ends a long timeout the bot was extending.
- Automatic actions: infraction thresholds and the Automations actions "Warn the member", "Timeout the member", "Kick the member" and "Ban the member" are recorded with the bot as the moderator. These add no infraction points, so an automatic action never escalates itself. An automation can record its case as hidden or keep it out of the case log, and its ban can be a timed ban (see the Actions Reference). (Members that anti-raid turns away at the door are not recorded as cases.)
- Discord AutoMod: when one of your AutoMod rules acts on a member, the bot records an AutoMod case with the rule type and the matched text, and adds the rule's infraction points.
While the module is turned off, actions in Discord and AutoMod are not recorded.
The case log
When a Case Log Channel is set, each new case is posted there as a message showing the case number and type, the reason, the duration and the points added, then the member (with their ID, join date and account age), the moderator (with their top role), any proof, and the time. The accent colour comes from Case Colours in Settings. The post updates itself when you edit the reason or add proof. Cases from the mass commands are not posted one by one; the batch gets a single Mod Logs entry instead, and an automation action with Post the case to the case log turned off leaves its case out too (the case is still recorded, and {case_url} in its DM is then empty).
The Mod Logs module can post its own entry for moderation events too, in whichever channel you route them to:
After a command, the moderator gets a private confirmation. The ban, kick, timeout and warn confirmations use templates you can change (see Variables):
Looking up a member
/cases member:@someone shows that member's 10 most recent cases, newest first, with the type, reason, moderator and time, and a green or red dot for active or inactive cases. With infractions on, it also shows the member's current points. It works for users who have left the server too: paste their ID into the member option. Hidden cases are left out and counted; add show_hidden:True to list them.
In the dashboard, the Cases tab lists every case except hidden ones. Use the type menu and Filters (Moderator, Target, Proof, After, Before) to narrow it down.
Hidden cases
A hidden case is a real case that stays out of the way: automatic cases you do not want to scroll past, for example. An Automations action records its case hidden when its Hide the case option is on, and you can hide or unhide any case with the eye icon on it in the Cases tab.
A hidden case still counts: it keeps its infraction points, a timed ban still ends on time, and it is posted to the case log like any other (its title says "(hidden)"). Only the lists leave it out:
/caseslists visible cases and adds a line such as "2 hidden cases not shown";show_hidden:Truelists them too, marked "(hidden)".- The Cases tab shows a Show 2 hidden button next to the case count when hidden cases match your filters. With it on, hidden cases are listed with a Hidden badge; Leave out hidden goes back.
Hiding or unhiding a case is recorded in the staff log as a case update.
Editing and deleting cases
- Open Moderation > Cases.
- Click the gear icon on a case to edit it. You can change the reason, remove proof and add text, a link or a file.
- Click Save.
Editing a case only changes the record; it never undoes or repeats the action. The trash icon deletes a case for good, together with its case log post and the proof files in the Proof thread. Deleting a case does not unban anyone or take points back.
Attaching evidence
Attach proof to any case by its number, from Discord or the dashboard. A case holds up to 25 proof entries.
| Command | Description | Options | Permission |
|---|---|---|---|
/proof file | Attach a file as evidence to a case | case_number (whole number): The case number to add proof tofile (file): File to attach as evidencespoiler (true/false; optional): Mark this file as a spoiler | Members with Timeout Members; shown by default only to members with Timeout Members |
/proof image | Attach an image as evidence to a case | case_number (whole number): The case number to add proof toimage (file): Image file to attachdescription (text; optional): Alt text / description for the imagespoiler (true/false; optional): Mark this image as a spoiler | Members with Timeout Members; shown by default only to members with Timeout Members |
/proof text | Add text evidence to a case | case_number (whole number): The case number to add proof totext (text): Text evidence or notes | Members with Timeout Members; shown by default only to members with Timeout Members |
/proof url | Add a URL as evidence to a case | case_number (whole number): The case number to add proof tourl (text): URL to evidence (image, video, screenshot, etc.)title (text; optional): Display title for the link (shown as hyperlink) | Members with Timeout Members; shown by default only to members with Timeout Members |
/proof textadds a note, such as a summary of what happened./proof urladds a link (http or https only);titleis shown as the link text./proof imageadds an image;descriptionis its alt text andspoilerblurs it./proof fileadds any file;spoilerhides it behind a spoiler.
Images and files are uploaded to the Proof thread in the case log channel, so /proof image and /proof file need a case log channel. Each entry records who added it and when, and the case log post lists them. In the dashboard, files you add to a case go to the same thread, up to the server's upload size limit.
Typical workflow
- Take the action:
/timeout member:@spammer duration:1h reason:Spam. Note the case number in the confirmation. - Attach the evidence:
/proof image case_number:131 image:<screenshot> description:The first spam message. - Add context later with
/proof textor from the dashboard.