Mod Logs - Overview
Mod Logs posts a log entry to your chosen channels whenever something happens in the server: a ban or warning, an edited or deleted message, a member joining or changing roles, a channel or role being changed, someone moving between voice channels, and more. There are 79 log types in six categories, and you decide per channel which ones it receives and which events it skips.
Mod Logs is off until you turn it on with the switch at the top of its panel, and it has no slash commands: everything is set up in the dashboard.
How it works
- You add a log channel: a text, voice or stage channel in your server.
- You pick the log types it receives. A channel with no log types receives nothing.
- Optionally, you add filters so the channel skips (Blocklist) or only keeps (Allowlist) events from certain channels, categories and roles, and skips events by bots.
- The bot posts entries through a webhook in that channel, which it creates for you. Entries that arrive close together are grouped into one message.
You can add as many log channels as you like and route each kind of event to its own place, for example moderation to #mod-logs and message edits and deletes to #message-logs.
What an entry looks like
Each entry is a Discord components message showing what happened, who was involved (with their mention and ID), who did it when Discord's audit log names them, and the details, such as the old and new text of an edited message:
Every log type uses a message template you can change; see Variables.
Pages in this guide
| Page | What it covers |
|---|---|
| Setup | Turning Mod Logs on, adding a log channel and routing recipes |
| Log Types Reference | Every log type and when it fires |
| Filtering | Allowlist and Blocklist filters, excluding bots, per-type overrides |
| Settings | Channel settings, webhooks, archives and the Logs tab |
| Variables | The templates and variables of every log type |
| Troubleshooting | Missing entries, missing moderators and other problems |