Moderation Module

Moderation

The control room for your staff: warns, mutes, bans, a mute role, DM ban messages, an appeal system, proof buttons, and where every mod action gets logged.

Where to find it: run /config Category dropdown Moderation Moderation. Toggle the module on first.

How it fits together

Moderation is a big module, but you only need a few things for a solid setup: a mute role so /mute works, log channels so actions are recorded, and command permissions so the right people can moderate. Everything else is polish you can add later.

Good to know

Don't try to set all 16 options at once. Do the four in the walkthrough below, then come back for warns, appeals, and proof when you need them.

Recommended first setup

  1. Permissions: choose which roles can run each moderation command. Without this, only members with Discord's built-in permissions can moderate.
  2. Mute Role: pick (or let the bot create) the role given to muted members, so /mute has something to apply.
  3. Channels: set the log channel(s) where mod actions are recorded, so your team can see who did what.
  4. (Optional) Warn System: turn on warns and set how long a warn stays active and what timeout it triggers.

Reference: all settings

SettingWhat it does
ChannelsThe log channel(s) where moderation actions are posted.
Main RoleThe main server role used by the moderation system.
PermissionsWhich roles are allowed to run each moderation command.
HideHide mode for moderation command usage (keeps commands discreet).
Warn SystemEnable and tune warns, active duration, default timeout, hide moderator, and more.
ReasonsManage preset reason inputs so staff pick from a consistent list.
Compact LogsShorter, denser moderation log output.
Mute RoleThe role applied to muted members.
Mute DurationDefault length for /mute when no time is given.
Ban PurgeDefault amount of a banned user’s recent messages to delete.
Ban MessageA custom message DM’d to a user when they’re banned.
ProofAdd “proof” buttons to mod actions so staff can attach evidence.
BlacklistThe preferred automod word blacklist.
AppealsA system letting punished members appeal a mod action.
Message ReportsThe channel where reported messages are sent.
Help PingsRoles pinged when a member asks for staff help.

Command options worth knowing

The full list lives on the commands page. These options change how the config defaults are applied:

CommandWhat it does
/mod warn muteOverride the timeout the Warn System would give for this one warn, e.g. 30m, 6h, 1d (1 minute to 4 weeks), or none to skip the timeout. Can't be combined with a verbal warn.
/mod quarantine reasonAdd a reason when quarantining or releasing someone. It shows in the security log and the audit log, and in the DM the member gets when quarantined.
/mod purgeThe options popup now has a Channel picker, so you can purge any text, voice, or thread channel without going there first. It defaults to the channel you ran it in.

Troubleshooting

ProblemFix
/mute does nothingSet a Mute Role, and make sure the bot’s role is above it.
A staff member can’t use a commandAdd their role under Permissions for that command.
No mod actions are loggedSet a log channel under Channels and check the bot can post there.
Ban DM never arrivesThe user had DMs off or shared no server with the bot after the ban.
“Verbal warns cannot include a mute”Leave the mute option empty (or set none) when using verbal: true.
Purge says you lack permissionsYou need View Channel, Manage Messages, and Send Messages in the channel picked in the purge popup. The bot needs View Channel, Manage Messages, and Read Message History there.