Action Logs

Action logs give your staff a record of what happened in the server and who did it. Someone gets banned, a role changes hands, a message disappears: it lands in a channel you choose, with a timestamp and a name attached.

There are six categories. Each one gets its own channel, so you can keep message logs away from moderation logs, or send the lot to one place with a single click.

Tier	Free
Command	/logs
Who can use	Admins
Also on dashboard	Yes

The six categories

Category	What lands in it
Server	Bans, unbans, kicks, members joining and leaving, prunes, server setting changes
Members	Nicknames, roles gained and lost, timeouts, username and avatar changes
Messages	Deleted, bulk-deleted and edited messages
Channels	Channels created, deleted, renamed, or having their topic, permissions or slow mode changed
Roles	Roles created, deleted, renamed, recoloured, or having their permissions changed
Voice	Members joining, leaving and moving between voice channels

A category with no channel set is simply off. Within a category you can switch individual events on and off, so you can log role changes without logging every avatar update.

Colours tell you the shape at a glance

• Green means something arrived. Someone joined, a role was granted, a channel was created.
• Red means something went away. Someone left or was banned, a message or role was deleted.
• Plain means something changed in place. A rename, an edit, a move between voice channels.

Permission changes stay plain on purpose. A single change usually grants some things and revokes others, so neither colour would be honest about it.

Deleted messages keep their text and their images

This is the part most log bots get wrong. Discord’s delete notification contains no message content at all, and the link to any attached image starts breaking the moment the message dies. A bot that waits until the delete to go and fetch the picture has usually already lost it.

Codex Helper saves images as they are posted, not when they are deleted. So when a message goes, the log entry shows the original text and re-uploads the images as real files you can open and download. They survive even though Discord has thrown the originals away, and they survive the bot restarting.

Give the bot Attach Files

In whichever channel receives your message logs, the bot needs Attach Files on top of the usual Send Messages and Embed Links. Without it the text still logs, but recovered images cannot be re-uploaded. /logs settings warns you if this is missing.

Images are kept for 30 days. Only servers that have message logging switched on are stored at all, so turning the category off stops it immediately.

Skipping people, roles and channels

Some things are not worth logging. A bot that posts constantly, a spam channel, a staff role whose every move you already trust.

Under Ignore list you can name any of three things:

• People. Nothing that person does is logged, at all.
• Roles. Nothing anyone holding that role does is logged.
• Channels. Nothing that happens in that channel is logged.

Each list holds up to 25 entries.

An ignored person produces no entry anywhere, not even a “something was deleted here” placeholder. Take them off the list and they start being logged again from that moment.

Who did it

Most of what Discord tells a bot is what happened, not who did it. For that, the bot reads your server’s audit log, which needs the View Audit Log permission.

Without it, everything still logs, entries just say nothing about who was responsible. /logs status tells you if the permission is missing.

Setting it up

1. Run /logs settings.
2. Either pick Send everything to one channel and choose a channel, which sets up all six categories and switches logging on in one step,
3. Or pick a category, give it a channel, and use Events to tick exactly what you want logged. Going category by category leaves the master switch off, so also pick Action logs: ON in the same menu when you are done.
4. Repeat for any other categories you want.
5. Check it with /logs status.

You can do all of this on the dashboard instead, under Action Logs. Changes there reach the bot within a minute, with no restart needed.

Commands

/logs settings

Opens the setup panel. One menu, from which you can:

• Turn action logs on or off for the whole server
• Pick a channel per category and tick individual events on or off
• Send everything to one channel in a single step
• Turn every event you have switched off back on

Only you can see the panel, and only the admin who opened it can change it.

/logs status

A read-only summary of which categories are on, which channel each one uses, and how many of its events are switched on. Also flags a missing View Audit Log permission. Nothing to fill in.

Good to know

• If a log channel is deleted, the bot quietly stops posting to it rather than erroring on every event. /logs settings flags the broken category.
• Other bots are logged too. If a bot posts an announcement and someone deletes it, that gets recorded. Codex Helper only skips its own log entries.
• Nothing is shared between servers. Your logs, settings and stored messages are yours alone.
• Turning a category off clears its stored data, so a server that stops using message logging stops being stored straight away.