Logging
Twelve server event types delivered as embeds to one log channel, with per-event toggles and honest skip rules.
The logging module forwards server events to a single log channel as embeds. There is one channel and twelve event keys; per-event toggles decide what is sent.
The event types#
| Event key | Logged as |
|---|---|
| messageDelete | Message deleted (content preview) |
| messageUpdate | Message edited (before / after) |
| channelCreate | Channel created |
| channelDelete | Channel deleted |
| roleCreate | Role created |
| roleDelete | Role deleted |
| guildBanAdd | Member banned |
| guildBanRemove | Member unbanned |
| ticketCreate | Ticket opened |
| ticketClose | Ticket closed |
| ticketReopen | Ticket reopened |
| moderationAction | Moderation action (from Kharat's own tools) |
Configure it#
Dashboard: set the log channel, tick the events you want. Slash: /logging channel #logs, /logging toggle event:<key> enabled:<bool>, /logging status for a green/red list, /logging test to post a sample embed. Both commands require Manage Server or Administrator.
What an embed looks like#
Every embed carries a title, a colour and a timestamp, with event-specific fields (content previews truncated to 1000 characters, before/after pairs for edits, user info for bans). Colours: deletions and bans red, edits yellow, creations and unbans green.
What is deliberately skipped#
- Messages from bots (no bot-on-bot spam).
- Message edits where the content did not actually change.
- Anything while the module, the server or the log channel is off.
- Events you toggled off.
Failure behaviour#
If a log embed cannot be delivered (missing permissions, deleted channel), the failure is throttled — at most one warning per channel per minute is written to the bot's console, so a broken log channel cannot flood logs. Fix the channel's permissions and events flow again.
Log channel requirements: View Channel, Send Messages, Embed Links. Announcement and text channels are accepted as targets.