Moderation

Every moderation action creates a case, DMs the user if you let it, and logs itself. The settings below decide what that looks like.

#Cases

A case is the record of one action: who, what, why, when, by whom, and any proof attached. Bans, kicks, mutes, warns and their undos all create one.

Each case has a short ID. Give that ID to /case view to pull it up, or /unwarn to remove the warning it recorded.

Reply to a message with t!ban and the replied message is captured as proof automatically, including the text, the author and any attachments.

/history shows every case on one user in order. It is the fastest way to answer "have we dealt with this person before".

#Editing a case

/reason changes the reason on an existing case. /caseupdate changes the reason or the duration. Both keep the original, so the case shows it was edited rather than quietly rewriting history.

#Punish settings

The defaults that apply to every action.

Purge pinned messages is off by default on purpose. Pins are usually pinned for a reason and a bulk delete that takes them is hard to undo.

#Immune roles

Roles that moderation cannot touch. Set globally, or per action, so staff can be immune to bans while still being muteable.

Immunity is checked before anything happens, so an immune user is refused rather than half-punished.

#Role hierarchy

With Use role hierarchy on, a moderator can only act on members below them in the role list. This stops staff from punishing each other sideways, and it is enforced separately from Discord's own hierarchy check on the bot.

#User notifications

What the user is told, and how much of it. Under Privacy:

Turning the author off is the common one. It keeps individual staff out of an argument with a banned user.

The DM itself is a template. Rewrite it under Messages, and put your appeal link in it. That stops most "I was banned unfairly" DMs to staff before they start.

#Predefined reasons

An alias that expands to full wording. Set raid to mean Participating in a coordinated raid on this server, and t!ban @user raid records the whole sentence.

They keep reasons consistent between staff, and they make the DM read like it was written rather than typed in a hurry.

#Warn thresholds

Escalation on a warn count. Three warns becomes a mute, five becomes a ban. You choose the count, the action and the duration.

Thresholds are checked after each warn, and the escalation creates its own case, so the record shows both the warn and what it triggered.

#Channel locking

/lock denies Send Messages for @everyone in the current channel. /lockall does it across the server.

Leaving Channels to lock empty means every text channel the bot can see. Set it if you want a staff channel to stay open during a raid.

#User reports

Members report a rule-breaking user to a channel your staff watches. Reports arrive with the reported user, the reporter, the reason and any linked message.

/report-blacklist blocks someone from reporting, for when the feature itself is being misused.

#Commands