Logging
Route whole logging categories or individual events, then verify delivery.
Choose a category or an event
You do not need to configure every logging event individually. Use ,logs add <event-or-category> #channel to route an entire supported category, or one individual event. Replace the bracketed argument; do not type the brackets. Logging configuration requires Manage Server. logging is an alias for logs.
,logs add members #member-logsAll supported categories
messages — message_delete, message_bulk_delete, message_edit
members — member_join, member_leave, member_update
moderation — member_ban, member_unban, member_kick, member_timeout, member_mute, member_unmute, member_jail, member_unjail, warning_action
voice — voice_join, voice_leave, voice_move, voice_state_update
channels — channel_create, channel_delete, channel_update
roles — role_create, role_delete, role_update
invites — invite_create, invite_delete
webhooks — webhook_update
emojis — emoji_create, emoji_delete, emoji_update
stickers — sticker_create, sticker_delete, sticker_update
server — guild_update, audit_event
threads — thread_create, thread_delete, thread_update
commands — command_used
security — security_action, automod_action
tickets — ticket_action
voicemaster — voicemaster_action
,logs categoriesJoins, leaves, actions, and other aliases
joins / join → member_join; leaves / leave → member_leave; actions / action / audit → audit_event. These are individual-event shortcuts, not extra categories. In particular, actions does not include every moderation, command, or security action.
Category aliases: message → messages, member → members, mod → moderation, channel → channels, role → roles, invite → invites, webhook → webhooks, emoji → emojis, sticker → stickers, thread → threads, command → commands, and ticket → tickets.
Other event aliases: ban, unban, kick, timeout, mute, unmute, jail, and unjail map to the corresponding member_ event; warnings maps to warning_action. Names are case-insensitive and hyphens are normalized to underscores.
,logs add joins #joins
,logs add leaves #leaves
,logs add members #member-logs
,logs add roles #role-logs
,logs add moderation #mod-logs
,logs add channels #channel-logs
,logs add actions #action-logsList or filter events
logs events lists all supported events alphabetically, with their category, in pages of up to 20. Add an optional category to filter the list: ,logs events moderation. A valid individual event name or alias also works and returns that one event. ,logs events joins therefore shows only member_join. An unknown selection is rejected.
,logs events moderationRouting and permissions
An individual-event route overrides its category route. Unconfigured events can still use the existing setup logging channel as a fallback. Adding a category re-enables all its events but preserves individual-event overrides. Repeating logs add updates that selection’s destination. The shorthand ,logs members #member-logs also works.
Choose a staff-only destination where appropriate. Blood must have View Channel, Send Messages, Embed Links, Attach Files, and Manage Webhooks in that channel. Use ,logs config (aliases: logs list, logs status) to review routes, options, disabled events, and ignore counts.
,logs add message_delete #deleted-messagesDisable and re-enable
logs remove <event-or-category> (aliases: logs disable, logs off) removes that selection’s explicit route and disables its events, including delivery through setup fallback or any remaining event overrides. Removing a category does not delete individual-event routes belonging to it; those events are disabled until re-enabled.
logs enable <event-or-category> (alias: logs on) re-enables the events but does not restore a deleted route. Use logs add again to restore a destination. Adding a category also re-enables all its events.
,logs remove moderationIgnore rules and options
logs ignore <channel/role/user> ignores that target globally; optional --event <event> restricts it to one individual event, not a category. logs ignore list shows the rules. logs ignore remove <target> [event] removes that target’s ignore rules, or just the specified exact event rule. Use the canonical event name for this removal.
Options use ,logs <option> on/off: bots, webhooks, attachments, timestamps, content, and executor. For example, ,logs webhooks on changes the option, while ,logs add webhooks #webhook-logs routes the webhook_update event.
Test delivery
logs test [event] sends one test through the actual configured route. The default is audit_event. It accepts individual events or their aliases, not entire categories: use ,logs test member_join to test a members destination. Disabled events, ignore rules, missing routes, and channel permissions can prevent delivery.
,logs test member_joinReset is not a disable-all command
logs reset clears explicit routes, options, ignore rules, disabled-event records, and stored webhook references. It does not clear the older setup logging configuration, so fallback logging can resume. There is no logs clear command. Use logs remove with a category or event when you want to disable delivery.
Command quick reference
Blood’s real command help cards, including syntax, examples, aliases, permissions, categories, cooldowns, and interactive paginator controls.
APPblood helpCommand: logs categories
Lists every configurable logging category
Syntax: logs categories
Manage ServerAPPblood helpCommand: logs events
Lists every event that can receive its own log channel
Syntax: logs events <category>Command: logs add
Routes a category or individual event to a log channel
Syntax: logs add (category or event) (channel)Example: logs add message_delete #message-logsCommand: logs config
Shows every logging route, option, and ignore count
Syntax: logs configCommand: logs remove
Disables an event or category, including setup fallback logs
Syntax: logs remove (event or category)Example: logs remove command_usedCommand: logs enable
Re-enables a disabled logging event or category
Syntax: logs enable (event or category)Example: logs enable command_usedCommand: logs test
Sends a test event through the configured webhook route
Syntax: logs test <event>Example: logs test message_deleteCommand: logs ignore
Ignores a channel, role, or member globally or for one event
Syntax: logs ignore (channel/role/user) <--event event>Example: logs ignore #staff --event message_editCommand: logs ignore list
Lists ignored logging channels, roles, and members
Syntax: logs ignore listCommand: logs ignore remove
Stops ignoring a logging channel, role, or member
Syntax: logs ignore remove (target) <event>Example: logs ignore remove #staff message_editCommand: logs reset
Resets all explicit logging routes, options, and ignores
Syntax: logs reset