Skip to main content

​
Overview

Moderation commands require some basic setup before they can be used. This includes mute roles, the jailed role & channel, and mod logs.
1

Creating the jail system

Jail restricts users from all channels except #jailed.
Use the ,setme command to create the jailed role and channel.
2

Creating mute roles

This creates muted, imuted (image mute), and rmuted (reaction mute) roles.
Use the ,setmute command to create the necessary mute roles.
3

Setting up mod logs

Use ,logs add #channel mod to set where moderation actions are logged.
Upon completion, you’ll have these roles:
  • muted - Restricts sending messages and speaking in voice
  • imuted - Restricts uploading attachments and embeds
  • rmuted - Restricts adding reactions
  • jailed - Restricts all channels except #jailed

​
Moderation commands

​
Invoke messages

Customize the channel response and DM sent when a moderation command runs. The following actions can be customized: jail, unjail, kick, ban, softban, hardban, unban, timeout, untimeout, warn, mute, unmute, imute, iunmute, rmute, & runmute.
The message can be raw text or an embed with dynamic variables. Punishment templates support {reason}, {duration}, {invite_url}, {moderator.color}, {moderator.mention}, and the rest of the Punishments variables.
Use view to preview a template, or none / clear / reset to restore the default.

​
Case history

adore tracks every moderation action with case numbers:

​
stripstaff

stripstaff removes all roles with moderation permissions (ban, kick, manage roles, etc.) and revokes fake permissions. Use this in emergencies when a moderator goes rogue.
Pair moderation with fake permissions so staff can only moderate through adore, not native Discord.