General

Learn more about the core events that SajuukBot lets you configure.

SajuukBot will be ceasing operations on March 31st 2024, due to a variety of factors. For more information, please refer to the announcement provided on the SajuukBot discord server and your options for migrating to a new bot.

The Events module represents all of the passive events that happen in the background which are not based on the use of a bot command. This section lets you configure how the bot should listen for these kind of background events in the context of:

• Which events it should be listening for

• Which events should require additional processing for audit log data

Every event has an enabled key which turns off the event. If an event is disabled, then no processing is done in any way on that event. Some events don't have an audit log key: this is because they do not query audit logs in any way.

Things to be aware of

The events section of the configuration is powerful. However, changing event settings can lead to unintended consequences which can create potential problems with bot functionality.

Only disable events if you know what you are doing. Otherwise, you should take the time to enable ALL events and then disable those which you know you don't need

If you disable an event from being processed, but you have a feature enabled where the event MUST be enabled in order to process the feature, you will invalidate the configuration of the feature.

These include things like Member Join, Member Leave, Message Reaction Add and Message Reaction Remove, all of which need to be enabled to use things like Member Persist, Anti Raid Joins and Pinboard.

With respect of the Message Edit and Delete events, you can add an options key to define channels, users or categories that the bot should ignore these events in. For example, a potential use case for this feature could be ignoring deletes or edits in modmail ticket channels, as these will likely clutter your modlogs unnecessarily.

This is a power user feature which you should not use unless you know what you are doing.

The AUTOMOD EXECUTED event is, by default, always enabled in a bot configuration, even when it is not defined.

The reason for this is that, should you choose to use the Discord AutoMod functionality with the setting to block messages enabled, the bot won't be able to properly track messages which get blocked by the AutoMod. If you don't need this functionality, just change the enabled key to false for this setting, but we recommend leaving it enabled.

In addition, this event requires the bot to have Manage Server. This is because Discord dispatches no data about the triggered AutoMod rule in the action event. If the bot does not have the correct permission, no modlog will be generated.

Event	Description
AUTOMOD CREATE	Log the creation of automod rules.
AUTOMOD DELETE	Log the deletion of automod rules.
AUTOMOD EXECUTED	Log messages blocked by the Discord AutoMod. This event is always enabled: you only need to add this for the purpose of disabling this feature, but this is not recommended.
CHANNEL CREATE	Log the creation of channels. An emoji is used to signify the type.
CHANNEL UPDATE	Log the update of channels. The updates that are tracked by this event include: - The channel name - Whether a slowmode was added via UI - The voice region [for Voice/Stages only]
CHANNEL DELETE	Log the deletion of channels. An emoji is used to signify the type.
GUILD UPDATE	Log the update of the guild. The updates that are tracked by this event include: - The guild name - The guild owner - The guild verification level. This will also passively check if your guild contains the PARTNERED and/or VERIFIED feature flags: this will not be logged but triggers icons on the dashboard.
INVITE CREATE	Log the creation of invites. This deliberately ignores invites generated by the Server Widget.
INVITE DELETE	Log the deletion of invites. This deliberately ignores invites deleted that belonged to the Server Widget. Alongside manual deletion of invites, this will be triggered on limited-use invites when users join the server using them.
MEMBER JOIN	Log the addition of members to the guild. You must enable this to allow Member Persist and Anti-Raid Joins to function!
MEMBER LEAVE	Log the removal of members from the guild. You must enable this to allow Member Persist to function!
MEMBER BAN	Log the banning of members from the guild. This does not need to be enabled to use any bot commands that ban members: it should only be enabled to track bans from the right click UI.
MEMBER UNBAN	Log the unbanning of users from the guild. This does not need to be enabled to use the !unban bot command: it should only be enabled to track unbans from the Bans UI in the client.
MEMBER UPDATE	Log the update of members in the guild. The updates that are tracked by this event include: - The members' nickname. - The members' roles. - The members' global display name. - The members' username. - Whether the member was timed out. Please note that turning off the logging of username changes only silences the modlog post: the event will always be dispatched and processed behind the scenes due to cache requirements.
MESSAGE DELETE	Log the deletion of messages in the guild. Messages which are not present in the backend database are ignored. Due to a Discord API limitation, this event cannot include information about who deleted the message.
MESSAGE EDIT	Log the update of messages in the guild. Only the content of the message is tracked, due to it also being dispatched whenever embeds are updated in some form, which is irrelevant.
MESSAGE REACTION ADD	Allow processing of Reaction Add events. By turning this off, reactions will not be processed beyond knowing that the event was dispatched by the API. Refer to the warning notice above about turning this off.
MESSAGE REACTION REMOVE	Allow processing of Reaction Remove events. By turning this off, reactions will not be processed beyond knowing that the event was dispatched by the API. Refer to the warning notice above about turning this off.
ROLE CREATE	Log the creation of roles. This will often be dispatched with the name new role as a result of the design of the Discord client: however, in some cases, it may be dispatched with the name already set (only on Mobile).
ROLE UPDATE	Log the update of roles. The only update tracked by this event is the role name: other updates, like the position and colour, are discarded.
ROLE DELETE	Log the deletion of roles. This will often be dispatched alongside MEMBER_UPDATE as a result of the role being removed from any members who possessed it at the time of deletion.
THREAD UPDATE	Logs when a thread is updated by its creator or a moderator. The updates that are tracked by this event include: - The thread name was changed - The thread was locked by a moderator. - The thread was unlocked by a moderator. Please note that turning off the logging of thread changes only silences the modlog post: the event will always be dispatched and processed behind the scenes due to cache requirements.
VOICE CHANGE	Log the changing of member voice states. This is not dispatched when members end up in a defined AFK channel. You must enable this to allow Voice Statistics tracking to function!