Moderation
Warn, mute, kick and ban, with history, a log channel and your own notifications.
In the panel under: Moderation, Moderation
The classic moderation tool. It provides the moderation commands and records every action, so a member's history is kept even when channels get cleaned up or the team changes.
Setup
Enable the module
Flip the switch at the top.
Set moderator roles
Only members with one of these roles can use the moderation commands. If you leave the field empty, nobody can moderate.
Set up the mute role
Click Create mute role. The bot creates the role and adds the matching restrictions in every channel, so a muted member really can't type anywhere anymore.
Choose a log channel
The bot posts an embed there for every action.
Save
Settings
| Setting | Meaning |
|---|---|
| Moderator Roles | Who can use the commands |
| Mute role | The role that /mute gives |
| Log channel | Where the action embeds go |
| Sanction DMs | The five DMs, see below |
Create and sync the mute role
Two buttons, one purpose.
- Create mute role creates the role and sets up the restrictions in every existing channel.
- Sync mute role adds missing channel permissions afterwards. The progress is shown live.
Commands
| Command | Effect |
|---|---|
/warn |
Warning with a reason, gets saved |
/warnings |
Show all warnings of a member |
/unwarn |
Take back a warning |
/mute |
Mute, with a duration |
/unmute |
Lift a mute |
/kick |
Kick from the server |
/ban |
Ban |
/unban |
Lift a ban |
/clear |
Delete several messages at once |
/moderation create-mute-role |
Create the mute role by command and set up all channels |
/report |
For members: report a member to the team, see below |
If Anti-Nuke is active, /kick and /ban count for the moderator who uses them, just like a kick or ban by hand. Whoever bans many members in quick succession during a raid can therefore show up as a mass ban. Trusted moderators belong on the Anti-Nuke whitelist.
The five notifications
When someone is banned, kicked, warned, muted or unmuted, they get a DM. You can freely design all five in the Message Builder under Sanction DMs.
Reports
Members report other members to the team without having to message a moderator directly. You turn this on in the Reports section and choose a channel that only the team can see.
Member reports
With
/report, plus the person and a reason, or by right-clicking a message, then Apps and Report message. The member only gets a private confirmation.Team gets a card
A card appears in the report channel with the reporter, the reported person, the reason and, for messages, the text, the attachments and a link to the spot. Optionally a role is pinged.
Team handles it
Take over, Done, Reject, Block reporter and an action: Warn or Timeout for 10 minutes, 1 hour or 1 day. Warn works exactly like
/warn, with history, DM and log.
| Setting | Meaning |
|---|---|
| Report channel | Where the cards go. Without a channel the bot doesn't accept reports |
| Ping role | Optional, mentioned on every new report |
| Wait between two reports | 1, 5, 15, 30 or 60 minutes per member |
| Roles that can't report | For example a punishment role |
| Notify reporter | DM to the reporter as soon as the report is closed. The moderator and action are not named |
| Blocked reporters | Blocked via the button on a report, unblock them here |
On every card, the bot checks on each click whether you are part of the team and whether your role is above the member's. If two moderators click at the same time, the action is still only carried out once.
Timed mutes survive a restart
A mute with a duration ends correctly even if the bot restarts in between. On startup, the bot reads all running mutes and restores the timers. Anything that would have expired during the downtime is lifted right away.
Required permissions
Kick Members, Ban Members, Manage Roles (for the mute role), Manage Messages (for /clear), Manage Channels (for syncing), Moderate Members (for the timeout on reports).