Logging for server activity and moderation actions. The logs plugin has no commands - it listens to Discord events, stores audit rows, and posts to configured channels when toggles allow it.

#Configuration

yaml

# Server events: joins, leaves, edits, deletes, channels, roles, voice, etc.
server_log_channel_id: "1234567890123456789"

# Moderation: infractions, automod, censor, cleans, voice mod, case updates
moderation_log_channel_id: "1234567890123456789"

# Per-event toggles (missing keys default to enabled)
logging:
  events:
    member_join: true
    message_delete: true
    voice_self_mute: false

Configure channels and toggles in the dashboard Logging section. Browse stored events in Logs.

The legacy log_channel_id field still works as a fallback for moderation logs if moderation_log_channel_id is not set.

Infraction case logs (warn/mute/kick/ban/etc.) always post to moderation_log_channel_id; there's no separate per-plugin override for them.

#Storage

Every enabled event is stored in guild_log_events for 90 days (used by the dashboard Logs page), even if no Discord log channel is set.

Message content snapshots for edit/delete reconstruction are still kept in log_messages for 42 days.

#Log layout (Discord)

Each Discord log is a Components v2 message:

Colorless container
Section with the member's avatar thumbnail (when available)
Bold title
Information block with labeled fields, snowflakes, and (where known) account-created / joined-server timestamps
Separator + extra block for message content, before/after edits, or a changes list
Up to 5 link buttons below the container — an automatic "Jump to Message" button when the event has a message, plus a "View in Dashboard" button, ahead of any event-specific buttons
Attached files when a field is too long to read inline (e.g. a long message body, a large before/after diff, or a big bulk-delete author breakdown) instead of silently truncating it

allowedMentions is disabled on every log message.

#Testing your log setup

The dashboard Logs page has a Test all logs button (Manage Server required). It fires one sample card per event type at your configured server/moderation log channels — titled 🧪 TEST — … — so you can see the full layout, buttons, and file-attachment behavior without waiting for something to actually happen. Test sends are not written to the 90-day log history.

#Server log coverage

Includes (toggleable): member join/leave/kick/ban/unban/timeout/nick/roles; message edit/delete/bulk delete/pin; channel and thread create/update/delete; role create/update/delete; guild update; emoji/sticker/invite/webhook changes; voice join/leave/move and mute/deafen/stream/video flags.

Where Discord provides audit logs, Dreamliner attaches the executor when available.

Bot accounts are excluded from member and message content logs.

#Moderation log coverage

Includes case create/update/delete/expire, automod, raid, censor, clean, voice mod actions, and failed DMs. Dashboard Logs can open the linked case when case_id is present.