Logs

Event logs send configured Discord activity messages to a selected channel. They are separate from protection logs.

Configure an event

Sign in, select your server and open Administration > Log. You must own the server or have Manage Server permission. April needs access to the destination and permission to send there.

1. Enable the general log setting and choose a default channel.
2. Select an available event and enable it. Add a nonempty message or embed; optionally enable its channel redirect and select a destination.
3. Save. In a test server, arrange an authorized event and check that the message arrives. For example, enable the member join event with a short message, then check the chosen channel after an authorized test member joins.

Both general and event settings must be enabled. A saved template or preview is not proof of delivery. See Formatting variables for message formatting.

General settings before saving. The current sender does not apply Ignore Bot.

The event form shows a neutral example before saving.

The preview is rendered in the dashboard; no event message was delivered.

Events and limits

The current Worker subscribes to member join and leave, ban and unban, voice join/leave/move, channel creation/deletion/update, and member updates. Channel create/delete handles text and voice channels; channel update handles name changes. Member update skips bots, prioritizes a nickname change and detects role changes when the role count changes; a same-count role swap is not detected by that branch. Handling depends on available Discord data; a source handler is not proof that every deployment delivers it. Username, avatar, discriminator, message edit/delete, mute and unmute identifiers exist but are not wired to equivalent event subscriptions here. A warning handler exists, but this subscription path does not establish a warning event source. Do not rely on a dashboard choice alone as evidence of delivery.

The current sending path does not apply the configured ignore-bot, ignored-role or ignored-channel settings. Treat those controls as ineffective for this path. Do not rely on them to suppress sensitive or noisy events.

Troubleshooting

If no message arrives, check that both settings are enabled, the event is wired, its template is nonempty, the selected destination exists and April can send there. A Forbidden or Not Found response during sending causes the Worker to disable that event; correct access and re-enable it. If the destination cannot be resolved from cache, the sender returns without disabling the event; check the channel and retry. Check actual Discord output after changing settings. If a message contains unwanted information, disable the event and revise its template; removing an already sent Discord message is a separate manual action.