Discord Logging Bot: Deleted Messages, Edits, Voice and Joins

What a log is for

Someone says a moderator insulted them. Someone deletes a message and denies writing it. A member leaves right after a raid. Without a log you have a story and nothing else. With one you have the text, the author and the time, in a channel only staff can see.

What Noxyr logs

Mute, deafen and streaming in voice are not logged. Account age on joins is handy at a glance, because a brand-new account joining during a raid stands out.

Set it up

1. Make staff-only channels, one per kind or one shared. Logs reveal message text, so keep them private.
2. Send each kind to a channel: /serverlogs set type: channel:, or use Safety, then Server Logs on the dashboard.
3. Add exclusions. /serverlogs ignore channel: skips a channel or a whole category. Add remove:True to log it again.
4. Check it. /serverlogs status shows where every kind of log goes. /serverlogs off type: stops one kind.

How it shows a deleted message

Here is the part that surprises people. When a message is deleted, Discord tells a bot only the message ID, not what it said. To show the text, Noxyr keeps recent messages in memory for 24 hours, only in servers that have a message log, and never writes them to disk.

That has two consequences you should know:

• A message older than 24 hours, or sent before the bot started, shows as not saved.
• Nothing about the text is stored permanently, which keeps the privacy cost low.

Tell your members that deleted and edited messages are logged for staff. It keeps things honest and avoids surprises.

Keeping logs useful

Logs are posted at most every few seconds per channel, ten entries at a time, so a raid or a big purge never floods your log channel. Even so, a noisy channel can drown out the rest.

• Ignore bot-spam and counting channels, which add many entries and no value.
• Ignore staff categories if you do not want moderators logged discussing cases.
• Give voice logs their own channel, since they are the busiest kind.

Pair it with other records

Message logs show what happened. Security modules show what was caught: anti-spam and anti-nuke each post to a log channel with the trigger that fired. The dashboard also keeps an activity log of settings changes with the Discord ID of who made them, for 30 days. Use anti-spam and anti-nuke next to your logs, and a warning system for the follow-up.

A starting layout that works

For a small server, one private channel called mod-logs is enough, with all three kinds pointed at it. As the server grows, split it into three channels so a voice-heavy evening does not bury a deleted message you need to find. Give access only to the staff who actually review logs, because deleted messages can contain private information a member meant to remove.

After setup, test it once. Post a message in a channel, edit it, then delete it, and check that all three events appear. If nothing shows up, check that the bot can see the channel and post in the log channel, and that you did not ignore the channel you are testing in with /serverlogs ignore.

Privacy and fairness

Logs are a trust tool, so treat them like one. Decide who may read them, write down when staff should look, and never use a deleted message as the only reason to punish someone. If a member asks you to delete their data, Noxyr handles that through the Support Center, as described in the data docs. Being open about what you log makes members more comfortable, not less.

Next steps

See the server logs docs. For what the bot keeps overall, read what the bot stores. If you are comparing bots, the best Discord logging bots lists options. Add Noxyr to start logging.