Before you start
- Create one or more private channels (visible to staff only) for the logs.
- Make sure Roody has access to those channels and the View Channel, Send Messages, Embed Links and Manage Webhooks permissions.
- For accurate moderation logs, give the bot View Audit Log.
Configuring from the dashboard
- Open /dashboard → Logs module.
- Turn on the module's main switch.
- Adjust the global parameters: embed colour, time zone, compact mode, whether to show thumbnails, and whether to include the bot's own events.
- Go through the category tabs and enable the events you want recorded.
- For each enabled event, pick the channel to send it to. You can send everything to the same one, or split by category.
Available events
Messages
Edits, individual deletions, bulk deletions (purges) and reactions.
Members
Joins, leaves, nickname changes, profile updates, bans, unbans and kicks. Also timeouts (applied and lifted).
Voice
Connections, disconnections, moves between channels, streaming, camera, mutes (self and server) and deafens.
Roles
Creation, deletion, editing, and assignment/removal from members.
Channels and threads
Creation, deletion and editing of channels and threads, plus per-channel permission changes and members joining/leaving threads.
Server
General changes (name, icon…), emojis, stickers, stages and invites.
Webhooks and integrations
Creation, editing and deletion of webhooks; integration changes (including other bots).
Discord's native AutoMod
Rules created/deleted/edited and executions (when AutoMod acts on a message).
Recommendations
- Separate sensitive categories into different channels: for example, one channel for moderation and another for voice/chat — that way the noise doesn't drown out what matters.
- Turn on "Compact mode" if you get a lot of events a day: each log takes up less space.
- Set the right time zone so the timestamps match your location.
- Disable noisy events on large servers (mass joins/leaves, reactions) if they flood the channel.
- Don't enable "Include bots" unless you're auditing another integration: it avoids noise.
Important notes
- Roody publishes the logs as webhooks; that's why it needs the Manage Webhooks permission in the target channel.
- Some events (who banned someone, who deleted a channel) require View Audit Log; without it, the log will show no author.
- Ticket logs live inside the tickets module itself, not here.
Troubleshooting
- No logs are arriving: check that the module is enabled, that the specific event has a channel assigned, and that the bot can write there.
- Logs show up with no author: the "View Audit Log" permission is missing.
- Too many logs: disable the events you don't use, or switch them to compact mode.
Comments
Share your experience or ask anything about this article.
Join the conversation
Sign in to leave comments and take part in the conversation.
Sign in