Moderation Features
TL;DR
Add moderation commands like warn, mute, kick, and ban.
Use auto-moderation rules to reduce spam and harmful content.
Keep your community safe and friendly with moderation tools built into your bot.
Available Moderation Tools
Manual Commands
Commands your mods can use when needed:
- Warn — Give users a warning
- Mute — Temporarily prevent users from chatting
- Kick — Remove users from the server
- Ban — Permanently remove and block users
Auto-Moderation
Automatic actions when rules are broken:
- Delete messages with bad words
- Remove spam or repeated messages
- Block links or attachments
- Slow down fast-moving conversations
Setting Up Mod Commands
When describing your bot, specify what moderation you need:
Basic Mod Commands
“Add /warn, /kick, and /ban commands. Only ‘Moderator’ role can use them.”
Full Mod Suite
“Moderation commands:
- /warn @user [reason] — Warn a user
- /mute @user [time] — Mute for a set time (like 10m, 1h)
- /unmute @user — Remove mute
- /kick @user [reason] — Kick from server
- /ban @user [reason] — Permanently ban All commands should log to #mod-log”
With Warning System
“Track warnings for each user. After 3 warnings, auto-kick. After 5 warnings, auto-ban.”
Mod Logging
Keep a record of all moderation actions:
“Log all mod actions (warns, kicks, bans) in #mod-log. Include:
- Who took the action
- Who was affected
- The reason given
- Timestamp”
Example log message:
⚠️ WARNINGModerator: @ModeratorNameUser: @UsernameReason: Spamming in #generalTime: Dec 14, 2024 3:45 PMAuto-Moderation
Bad Word Filter
“Automatically delete messages containing slurs or profanity. DM the user a warning.”
Spam Protection
“Delete messages if a user sends more than 5 messages in 10 seconds. Auto-mute for 5 minutes.”
Link Filtering
“Delete any messages containing links unless the user has ‘Trusted’ role.”
Caps Lock Filter
“Delete messages that are more than 70% capital letters.”
Permission Setup
Control who can use moderation commands:
Role-Based
“Only users with ‘Moderator’ or ‘Admin’ roles can use mod commands”
Command-Specific
“/warn and /mute for Moderators. /kick and /ban only for Admins.”
Self-Protection
“Prevent mods from using commands on each other or on admins”
Mute Setup
Muting requires a “Muted” role. Your bot can create and manage this:
“When someone is muted:
- Give them the ‘Muted’ role
- Remove the role after the mute expires
- If they leave and rejoin, reapply the mute”
Warning System
Track warnings across your server:
Simple Warnings
“/warn @user [reason] — Adds a warning. /warnings @user — Shows all warnings for a user.”
Progressive Punishment
“Track warnings:
- 1 warning: Just a warning
- 3 warnings: Auto-mute for 1 hour
- 5 warnings: Auto-kick
- 7 warnings: Auto-ban”
Warning Decay
“Warnings expire after 30 days of good behavior”
Appeal Process
Give users a way to appeal punishments:
“When someone is banned, DM them with an appeal link. Log appeals in #appeals for mods to review.”
Best Practices
Be Consistent
Apply rules the same way to everyone.
Give Reasons
Always require reasons for mod actions. It helps with transparency and records.
Start with Warnings
Don’t jump straight to bans. Use warnings and mutes first.
Keep Logs
Always log mod actions. You’ll want records if there are disputes.
Set Up #rules
Make sure your server rules are clear so users know what’s expected.
Example Mod Bot
“A moderation bot for a gaming community:
Commands (Mod role only):
- /warn @user [reason] — Warn user, log it
- /mute @user [duration] — Mute temporarily
- /kick @user [reason] — Kick with logged reason
- /ban @user [reason] — Permanent ban
- /warnings @user — See user’s warning history
- /clearwarnings @user — Clear all warnings
Auto-mod:
- Delete slurs immediately
- 5+ messages in 10 seconds = auto-mute 10 minutes
All actions logged in #mod-log”