Event Logging

bore can post a message every time something happens in your server, in as many or as few categories as you want, routed to whichever channels you pick.

Every logging command needs Manage Server (real or fake).

The fast way in

,logs setup

Two steps: tick the events you want, then choose the channel. Done.

,logs aio #logs

Everything, all twenty three event types, into one channel. Handy on a small server, noisy on a big one.

,logs panel

The same thing as a live panel: pick events, pick a channel, press Save. The panel also has All On and All Off buttons. Events that already had a channel keep it unless you explicitly choose a new one.

One event at a time

,logs add message_delete #mod-logs
,logs remove message_delete
,logs disable member_join
,logs enable member_join

add sets the channel and switches the event on. disable keeps your channel but stops the posts, and enable restarts them without you configuring it again. Running disable with no event stops every event at once.

Seeing what is configured

,logs events
,logs status
,logs config
,logs stats

events pages through every category and shows the channel, "Disabled", or "Not configured" for each one. status gives counts, config gives a summary including how long bore remembers ignored entries, and stats shows which events happen most in your server.

Testing

,logs preview member_ban
,logs test member_ban

preview shows you what the embed looks like, right where you typed. test actually sends one to your configured channel, which also proves the channel is reachable.

The events

Type them exactly like this. Case does not matter.

What you actually get in each:

• message_delete shows the author, channel, and the text that vanished.
• message_bulk_delete fires when two or more messages are cleared at once and names the biggest offenders.
• message_edit shows before and after, and only when the text really changed.
• member_join includes how old the account is and the server's member count, which is your best early warning for an alt wave.
• member_leave shows when they joined and which roles they held.
• member_ban and member_unban name the moderator when bore can read the audit log.
• member_update covers nickname changes, roles added and removed, and timeouts applied or lifted.
• channel_update, role_update and guild_update show what changed, such as a permission being flipped or the server banner being replaced.
• voice_state tracks joins, leaves, moves, and mute, deafen and self-mute changes.
• thread_update covers archiving and locking.

Bore's own messages and bot members are never logged, and pointless no-change updates are dropped so your channel does not fill with noise.

Skipping people, roles and channels

,logs ignore user @member
,logs ignore role @Bot
,logs ignore channel #bot-spam
,logs ignore list
,logs unignore channel #bot-spam
,logs unignore all

Anything caused by an ignored target is dropped before it reaches a channel. This is how you stop a busy bot channel or a music bot's voice activity from drowning your logs.

Keeping it tidy

,logs retention 60

Between 1 and 365 days, thirty by default. This is how long bore remembers the ignore rules above before forgetting the ones pointing at a member, role or channel that no longer exists. It never deletes anything in Discord.

,logs cleanup

Forgets those dead entries immediately.

,logs clear

Deletes every log setting for your server, after a confirmation button.