Logging
Event logs, moderator history, and protecting cases by role hierarchy.
Replace [prefix] with your server's prefix.
Event Logs
// Syntax
[prefix]logs [type] [channel]
// Example
;logs messages #message-log
;logs members #join-log
Each type is set separately, so you can route everything into one channel or split it across several. Running a type without a channel turns that log off.
| Type | Logs |
|---|---|
messages | Edits, deletions and purges |
members | Joins, leaves, nickname and avatar changes |
roles | Role creation, deletion and edits |
channels | Channel creation, deletion and edits |
guild | Server settings changes |
voice | Voice joins, leaves and moves |
invites | Invites created and deleted |
webhooks | Webhook changes |
bots | Bots being added |
emojis | Emoji changes |
stickers | Sticker changes |
threads | Thread creation and deletion |
;logs settings // what's currently going where
;logs setup // set every type up at once
[prefix]logs setup creates the channels and points every type at them in one
go. Faster than twelve commands, and you can move individual types afterwards.
Moderation Log
Separately from event logs, every punishment Serenity issues can be written to one channel:
// Syntax
[prefix]modlogs logs [channel]
// Example
;modlogs logs #mod-log
Moderator History
// Syntax
[prefix]modlogs [moderator]
// Example
;modlogs @moderator
;ml @moderator
Everything that moderator has done. The other direction — everything that has happened to a member — is:
;history @member
Both need Manage Server.
;modlogs top
Ranks your staff by how many cases they've handled.
Hierarchy Protection
;hierarchy enable
;hierarchy disable
With hierarchy on, a moderator can't undo a punishment issued by someone above them in the role list — no quietly unbanning what a senior moderator banned. Administrator only.
Hierarchy compares roles at the moment of the undo, not at the moment of the punishment. Promote someone and they can suddenly reverse older cases.