Logging

Logging records what happens in your server: messages edited and deleted, members joining, leaving and being moderated, roles and channels changing, voice activity, giveaways. Every event is switched on separately and sent to its own channel, so you decide exactly what is recorded and where it lands.

#The event catalog

There are sixty events, grouped into fifteen categories. The categories are for finding things — on the dashboard each one has All on and All off — but the setting itself belongs to the event: each of the sixty has its own on/off switch, channel and embed color.

#Setting it up

1. 01
   Open Logging on the dashboard

   Every event is a tile. Click one to open its settings, or select several — shift-click a range, ctrl- or cmd-click individual tiles, or drag a box — and change them together.

2. 02
   Pick a channel

   Picking a channel also turns the event on. An event that is on but has no channel posts nothing. The dashboard refuses to save a channel the bot cannot send messages in, rather than accepting it and staying silent.

3. 03
   Pick a color

   Each event has its own embed color, #5865f2 by default. Giving related events the same color makes a shared channel easier to scan.

4. 04
   Or use a command

   /log setchannel action:<event> channel:<channel> sends one event to a channel and turns it on. The action name autocompletes. Turning an event off and changing its color are done on the dashboard.

#Routing

Because every event has its own channel, splitting is free. Splitting is the difference between a log you read and a log you scroll past.

• Message events are the highest volume by a wide margin. Give them their own channel.
• Bans, kicks and timeouts are rare and the ones you most want to see. A channel that holds only those gets read.
• Voice joins and leaves produce an entry every time a member uses voice. Turn them on only if someone will look at them.
• Everything else can share a channel until it does not.

There are no ignore lists: an event that is on is logged wherever it happens in the server. Epix does skip its own posts in log channels, so a log entry is never reported as an edited message.

#What the bot needs

#What an entry shows

• The responsible moderator, when the audit log names one, and the reason, when one was given.
• Message edited: before and after, each cut at 1,024 characters, with a link to the message. Only a real edit counts — a link preview loading or a message being pinned is not logged as an edit.
• Message deleted: the text, stickers and attachments. Up to ten attachments of 25 MB or less are re-uploaded with the entry, so they outlive Discord's expiring links.
• Message text comes from Epix's own copy of the message. A message Epix never stored is logged without its text.
• Voice: a member leaving or switching channels is told apart from a moderator disconnecting or moving them.
• Member joins, leaves, kicks and bans show the account's creation date.

Who deleted a message

Discord folds repeated deletions into a single audit log entry, so a deleted message cannot always be pinned on one person. Without Premium, an entry Epix cannot attribute is recorded either as the author deleting their own message or, when a moderator recently deleted that member's messages in the same channel, with both of them listed as suspects. On Premium servers Epix reads the audit log itself and compares the counts to name the moderator.

#Commands

All of them require Manage Server.

#External webhooks

On Premium servers, any event can also be copied to a Discord webhook outside your server — a staff server, for example — from the dashboard or with /log external-set. The copy is made only when the event is on and has a channel in your server. Attachments are not forwarded. If five deliveries in a row fail, each within five minutes of the last, Epix turns forwarding off for that event.

#Action history and /who

On Premium servers, Epix also keeps a searchable history of moderator actions — bans, kicks, timeouts, nickname and role changes, voice moves and disconnects, server mutes and deafens, deleted messages, changes to channels, threads, roles, webhooks, emojis, stage instances, scheduled events, soundboard sounds and the server itself, and giveaway changes. Records are kept for 30 days. Without Premium nothing is recorded, and /who says so.

• action — the kind of action, with autocomplete (for example ban, timeout or rolegiven). Leave it out to search every kind.
• user, role or id — what the action was done to. id also accepts a custom emoji.
• executor — only actions performed by this member. It is ignored when a target is also given.

Give at least one of them. Results show who did it, to what, when and why, five to a page, covering the 50 most recent matches.

/who action:ban user:@member
/who action:rolegiven user:@member role:@Moderator
/who executor:@moderator