Skip to main content
Logging answers “what actually happened” after the fact. Vetox can record 154 distinct events, each configured independently.
Logging is free. Three options within it — showing who performed an action, posting via webhook, and the bulk setup tool — require Basic.

​
The screen

A tab strip with All plus sixteen categories, each showing how many of its events are enabled. Every tab has a search box and a running count of enabled events.

Server

Moderation

Messages

Channels

Roles

Emote Zone

Voice

Threads

Events

AutoMod

Stage

Webhooks

Integrations

Giveaways

Games

Battle Pass

​
Configuring an event

Every event is off by default and has its own settings.
A channel and a webhook are mutually exclusive. Setting one clears the other. You cannot send the same event to both.
On Starter, a Webhook URL is silently reset when you save — no error, no warning, the value simply reverts.If that setting will not stick, that is why. Everything else on the event saves normally.
The Disabled Channels exclusion only exists on message events. There is no per-channel exclusion for voice, role or moderation events.

​
Show Executor

Show Executor adds who performed the action to the entry: the moderator who banned, the admin who renamed a channel. 111 of the 154 events support it. The rest have no single actor, such as a member joining or an event starting on schedule. It follows your plan on its own:
Vetox reads the executor from Discord’s audit log, so the bot needs the View Audit Log permission. Without it the entry is still posted, without a name.
When a moderator acts through a Vetox command — ban, kick, timeout, mute and the like — the entry names that moderator, not the bot. For anything else Vetox does on someone’s behalf, such as AI Server Control or tickets, the entry shows Vetox together with the reason, which says who asked.

​
What the bot needs

​
When only the general event is enabled

Some actions have a specific event and a general one. If only the general one is enabled, the action is recorded there instead of being lost.

​
Setting up many events at once

Configuring 154 events individually is impractical, so Manage Logs creates channels and wires up events in bulk. Requires Basic. You also choose which roles may view the created channels, and which channels to exclude. Created channels deny @everyone and grant only the roles you nominate. The dialog reports progress through creating channels, assigning logs, setting permissions and applying exceptions.
Category mode is almost always the right choice. Individual mode across a broad selection creates a very large number of channels — up to 154.

​
Saving

Only events you actually changed are sent, so saving a single toggle does not rewrite your whole configuration.
Dashboard Watcher records enabling and disabling an event, and switching Show Executor on or off. Changing a channel, webhook or colour is saved correctly but leaves no audit entry.

​
Choosing what to log

These are the ones you will actually go back and read.
Edit and delete logging on a large active server produces an enormous amount. Use the disabled-channels option to exclude your busiest channels — this is the one category where you can.
Members joining and leaving voice generates constant entries. Log these only if you specifically need them.
A Discord AutoMod rule can block a message, send an alert and time the member out at once. Vetox records that as a single entry listing every action taken.
A webhook destination keeps working if the channel is renamed or moved, and posts without the bot needing send permission there. Requires Basic.

​
Troubleshooting

Check that Logging is switched on in Server Setup, then that the specific event is enabled and has a destination.
It requires Basic. Below that tier it shows as off, and it comes back by itself when the server subscribes.
Check that Show Executor is on for that event and that the bot has View Audit Log. Some actions have nobody to name: a member leaving voice by themselves, or a thread archiving after inactivity.
The bot is missing a permission. Webhook and integration events need View Audit Log; AutoMod events need Manage Server.
Webhook destinations require Basic.

Dashboard Watcher

Tracks changes made in the dashboard, rather than in Discord.

Moderation Tools

Review and lift punishments currently in force.