Event Logger
Logs server activity split into categories you can turn on/off individually, each falling back to one default channel unless you give it a channel of its own.
Setup
$logs
Also $log, $eventlogger, /logs. Opens a panel with four
dropdowns and a few buttons: pick a default channel, choose which categories are on, then optionally
route one specific category to its own separate channel. Picking a default channel or routing a
category's channel both auto-enable logging - there's no separate on/off step required to get
started.
$logs setchannel <#channel>
$logs on / offText-only shortcuts for the same panel actions, if you'd rather not click through it.
Pixie also needs the View Audit Log server permission (separate from the log channel's own permissions) to attribute who actually did what in logged events.
Categories
New servers start with a minimal default: Messages, Member join/leave, Moderation, and Pixie Mod Actions on; everything else off until you turn it on. Reactions and Username/avatar changes default off everywhere regardless, since both are high-volume. Two categories are Pixie-specific rather than raw Discord events:
| Category | Covers |
|---|---|
| Pixie Mod Actions | Every mod action run through Pixie's own commands - warns, bans, timeouts, nickname changes, jail, role changes, and more |
| Ticket Logs | Tickets opened, claimed, closed, deleted, and transcripts sent |
Servers that already had logging configured before these minimal defaults shipped keep whatever they already had - this only changes what a genuinely new setup starts with, nothing was silently turned off for existing servers.