Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.brewbot.dev/llms.txt

Use this file to discover all available pages before exploring further.

Mod logs record server events and moderation actions in a channel you choose. Each enabled event posts a color-coded embed with a short summary plus structured fields, so moderators can scan what happened without opening Discord audit logs. Most events now include who performed the action (the actor) by cross-referencing Discord’s audit log. This requires the View Audit Log permission — check Permissions if actor fields aren’t showing.

Configure mod logs

1

Open the dashboard

Go to the BrewBot Dashboard and select your server.
2

Navigate to Mod Logs

Open the Mod Logs page from the sidebar.
3

Select a log channel

Choose the channel where the bot should post log entries. You can also create a new #mod-logs channel directly from the dashboard.
4

Enable logging

Turn on the Enable Audit Logging toggle.
5

Choose events to log

Enable the event categories you want to track. Each event has its own toggle, so you can keep the log channel focused on what your team actually reviews.
Enable only the events you care about. Message edits, deletions, and high-churn channel updates can make the log channel noisy if you turn everything on at once.

Additional settings

  • Ignore bots — skips events when the affected user is known to be a bot
  • Hide user thumbnails — removes user avatars from member, message, and voice embeds
  • Ignored channels — skips message delete and message edit logs for the channels you exclude

Event reference

Each log entry uses a color to signal what kind of action happened:
  • 🟢 Green — joins, creates, unbans, and other positive or additive events
  • 🟡 Yellow — edits, updates, moves, and changed settings
  • 🔴 Red — leaves, deletes, bans, and removals
  • 🔵 Blue — informational events such as invite creation
  • 🟠 Orange — reserved for moderation warning-style events

Member events

Logs when a member joins the server.
FieldValue
ColorGreen
TitleMember Joined
SummaryMember mention joined the server
DetailsAccount created timestamp, account age, New account vs Established account, bot flag, custom avatar flag, invite code + inviter (if trackable), member count
FooterUser ID

Message events

Logs when a message is deleted. Ignored channels are skipped.
FieldValue
ColorRed
TitleMessage Deleted
SummaryMessage from a user was deleted in a channel
DetailsAuthor, deleted by (if a moderator deleted it), channel, original send timestamp, age at deletion, content length, attachment/embed/sticker counts, content preview, attachment names
FallbacksAttachment-only messages are labeled as such, and uncached partial deletes still log whatever data is available
FooterMessage ID

Role events

Logs when a role is created.
FieldValue
ColorRole color, with green fallback
TitleRole Created
SummaryRole mention was created
DetailsCreated by (actor), name, color, position, mentionable, hoisted, managed, permission count, truncated permission list
FooterRole ID

Channel events

Logs when a channel is created.
FieldValue
ColorGreen
TitleChannel Created
SummaryChannel mention was created
DetailsCreated by (actor), name, type label, category, plus type-specific fields such as topic, slowmode, NSFW, bitrate, or user limit when relevant
FooterChannel ID

Voice events

Logs when a member joins a voice channel.
FieldValue
ColorGreen
TitleJoined Voice Channel
SummaryMember mention joined a voice channel
DetailsChannel name, current occupancy, self mute/deaf state, stream state, video state
FooterUser ID

Server events

Logs when server settings change.
FieldValue
ColorYellow
TitleServer Updated
SummaryServer settings were updated
DetailsOnly changed fields are shown. Changes can include name, icon, banner, verification level, default notifications, AFK channel, and AFK timeout
FooterServer ID

Default settings

Moderation events such as Member muted, Member unmuted, Moderation ban, and Moderation unban are enabled by default in the dashboard configuration. The current event-driven log output described on this page focuses on the handlers already implemented by the bot, while all other toggles start disabled until you opt in.