Keep Discord message changes and moderation actions visible

What it needs

• The bot needs View Channel, Send Messages and Embed Links in the Audit Log Channel. Moderator actions and deleted-message attribution use the server-wide View Audit Log permission. It uses Server Members Intent for member changes and Message Content Intent for message logging.
• People using the Discord setup and configuration commands need Manage Server.
• The archive requires Pro to enable, search, view status or export. Manage Server is required for every archive action. Search and export also check your current View Channel and Read Message History permissions in the chosen source channel. Text and announcement channels only; deleted channels and threads cannot be queried.

Setting it up

1. Open Logging in your bot’s module settings and select an Audit Log Channel. The picker only offers text and announcement channels.
2. Choose a Quick Preset (Minimal, Standard or Comprehensive), or turn on the individual event settings you want under Messages, Members, Moderation, Server and Voice. Turn on Moderator actions and choose its channel; it starts with the Audit Log Channel. New bots enable it by default; existing bots keep it off until you opt in.
3. Use the Events Enabled and Voice Logs status chips to confirm that the events you expect are enabled, then run !testlog to send a test embed to the selected channel.
4. After generating or regenerating a Pro bot with Logging selected, enable Message Deletions (and optionally Bulk Deletions) and choose a log channel. In Discord, run /log archive action:on for each server you want to opt in. This is a separate Discord-only setting; saving dashboard logging settings does not enable it. Use action:status to check it.

Example

With Moderator actions enabled, banning Maya posts a Member Banned embed with User: @Maya and Moderator: @Alex when a recent matching Discord audit entry exists. If Discord does not record a matching actor, the field says Moderator unknown. A member leave is called a kick only when a recent matching kick entry exists. Attachments are included in message-delete logs when the message was cached.

Limits and troubleshooting

Limits

• Every event toggle is off by default, so the module logs only the event types you enable.
• Bot-authored messages and direct messages are not logged. The message cache keeps the latest 1,000 messages; a delete or edit outside that cache can show Content not cached.
• Each before, after, content or attachments field in a message log is capped at 1,024 characters. Duplicate events with the same type and target are skipped for five seconds.
• Moderator attribution is best-effort: if no recent matching audit entry exists, a moderator action says Moderator unknown. A member leave is never labelled a kick without a matching kick entry.
• The archive is off for new and existing servers until a manager enables it in Discord. Only future observed deletion events are saved. There is no old-message fetch, offline backfill, attachment storage, edit history or extra actor attribution in the archive.
• Archive records are retained for up to seven days, up to 1,000 per server and 10,000 across the bot. The oldest records are evicted first; busy servers can reach capacity before seven days. Expired records are pruned on archive access and by minute maintenance while the bot runs. Restarted bots prune before archive access; expiry cleanup pauses while offline.
• Each archived message stores IDs, the observed deletion time and up to 4,000 text characters. JSON content_source labels text supplied with the deletion event, an earlier message-cache snapshot or unavailable content. A cached snapshot can predate an edit; unavailable text is not recovered after restart. No deletion actor is inferred.
• Search shows five previews per page, capped at 100 characters each, without mentions or message formatting. JSON exports include up to 100 full saved records per page. Page numbers run from 1 to 200; pages are live snapshots and can shift as records arrive or expire. Keep downloaded files private.
• Disabling the archive stops capture and erases its saved records for that server. Clear erases records while preserving the opt-in. Neither action removes posted Discord logs or downloaded files. Regenerating without Logging stops commands and maintenance; unexpired local records can be accessed again only after the module is restored with Pro and the relevant permissions.

If it doesn’t work

• No entries arrive: select an Audit Log Channel and enable the matching event toggle. Output stays disabled until a channel is selected.
• A join, leave, edit or delete is missing: enable Server Members Intent and Message Content Intent in the Discord Developer Portal, then make sure the matching event toggle is on.
• The bot cannot post a log: give it View Channel, Send Messages and Embed Links in the Audit Log Channel.
• Moderator is unknown: turn on Moderator actions and grant the bot View Audit Log at the server level. Discord can omit an audit entry, and the module does not guess.
• No archive results: confirm Pro, run /log archive action:status, and check the deletion event toggle and log channel. Select the source channel, not the log channel. Only deletions observed after opting in are eligible; missing text, expiry and capacity can reduce results.