Skip to main content
The server log keeps a running record of everything that happens in your server — deleted messages, edits, people coming and going, bans, voice movement, role and channel changes, and more. You can send every event to one channel, split events across several channels, or fine-tune exactly what gets recorded and where.

Set Up Logging

Quickest route: run /logging setup. Newt builds a hidden category of log channels, points each event type at the right one, and switches everything on in one go. Run it a second time and it reuses what’s already there rather than creating a second set. Single channel: run /logging channel and pick where all logs go. Everything is switched on at once. Fine-grained control: open the Logs section on the dashboard, or use /logging event to route individual event types to their own channels.

Four Logs

All four logs answer to the /logging commands.
  1. Server log — records everything that happens in the server, however it happened (13 event types).
  2. Moderation log — records only punishments from Newt’s own moderation commands, with case numbers.
  3. Deleted media — keeps the actual image, video, or voice memo file when a message containing one is deleted.
  4. Survey reminders — records reminders sent to new members and how many people each reminder reached.

13 Event Types

Deleted messages · Edited messages · Bulk deletions · Joins · Leaves · Bans · Unbans · Nickname changes · Role changes · Voice channels · Channels · Roles · Server settings

Voice Log Notes

The voice log covers joining, leaving, and moving between voice channels. Muting, deafening, streaming, and turning on a camera are intentionally left out. Bots are excluded too — a music bot that rejoins on every track would bury all the real activity.

Overlap Handling

When both the server log and moderation log are active, a /ban placed through Newt appears once as a numbered case rather than showing up in both logs. A ban placed directly through Discord has no case number, so the server log records it as normal.

Deleted Media

Discord destroys a file the moment its message is deleted. Newt downloads a copy while the message still exists and posts it to your media log channel when the message goes. Coverage starts the moment you switch it on — files posted before the bot last restarted may not be recoverable, but the deletion is still logged with the filename and size. Files over 8 MB are not kept, though the deletion is always recorded. Without the View Audit Log permission, Newt can’t identify who deleted the message and will say so rather than guess. Note that someone deleting their own message leaves no audit entry at all, so that case always reads as unknown.

Ignore List

The dashboard’s Logs tab has a list of channels the log ignores. Nothing that happens in a ticked channel is recorded — deletes, edits, purges, voice activity, renames, or deleted media. Threads follow their parent channel.

Pausing Logs

Use /logging pause to mute the server log and media log for a set duration — useful during raid cleanup so the logs aren’t flooded while you work. The maximum pause is 6 hours; logs resume automatically when the time is up, or sooner with /logging resume.

Commands