Multi Modlogs

Understand how to configure SajuukBot to have multiple modlog channels containing a subset of events from the primary modlog.

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 primary / master modlog channel is very powerful, but because it contains all events received by the bot, it can be very difficult to navigate it unless you have had experience of knowing what to find.

SajuukBot makes it easy to manage what content you want to really see with a multi-modlogs feature. With this, you can set up as many channels as you wish that accept subsets of the events that go to the primary modlog channel. Therefore, if you want a channel that only records every moderation event (warn, kick, softban and so on), you can configure this to get just a filtered element of the modlogs that is far less spammy and significantly more searchable.

Configuration

Please be aware that Multi Modlogs is a dynamic feature which will vary from guild to guild. The configuration snippet below represents the generic (default) input which should be modified to suit your needs.

  extra:
    1234567:
      enabled: false
      events:
      options:
        hide issuer: false
        timestamp: false

Settings

To configure the multi modlogs requires duplicating the above code snippet (everything UNDER the root key extra) for every channel that will serve as a separate modlog channel. The key value (ie the 1234567 in the example above) should be replaced with the Channel ID for each channel. Each ID needs to be unique.

Under each key is the same 3 settings, which will be discussed below

Setting	Description
enabled	Toggles the state of this defined modlog channel. If this is false, then it will not be used to send messages for any defined events.
events	A list of strings representing named events that are to be sent to this channel. As with all lists, this can be given either using Python's standard list format or via YAML's hyphen format. The values you may use here are given at the end of this page.
options	Additional options that toggle different behaviours in the modlog channel: hide issuer: Toggles the visibility of the issuer of an infraction. If this is enabled and the defined channel is public, the issuer will be stripped from the content before being sent. timestamp: Toggles the visibility of the customised timestamps. These format and behave exactly like the primary modlog. If this is disabled or not defined, timestamps will not be shown.

In hide issuer, the description above specifies that it only applies to a public channel. Due to the nuances of how channel permissions can be defined, the bot only considers a channel "public" if the @everyone channel permissions are either set to a grey tick (meaning to inherit from role permissions) or an explicit ALLOW. If the channel has been set whereby the @everyone channel permissions are explicitly DENYING the permission (ie a red cross), it is not considered public and the setting will do nothing.

The hide issuer setting is deprecated and does not work if the issuer has a "unique username" (ie they do not have a discriminator). This feature will be removed in an future update.

Events

For multi modlog channels to work, you need to define which events are to go into them. Any number of the values below the example may be placed as strings into the events setting described above.

For example, if you want a separate modlog channel that just logs all triggers of automoderators (Censors, Filters and Heuristics) to a channel with the ID 301395679908069378, then you would create a config like this:

  extra:
    301395679908069378:
      enabled: true
      events:
      - CENSOR_DUPES
      - CENSOR_FLOOD
      - CENSOR_ATTACHMENTS
      - CENSOR_MENTIONS
      - CENSOR_NEWLINE
      - CENSOR_LINKS
      - MINI_CENSOR_EMOJI
      - MINI_CENSOR_ATTACHMENTS
      - MINI_CENSOR_MENTIONS
      - MINI_CENSOR_NEWLINES
      - MINI_CENSOR_DUPLICATES
      - MINI_CENSOR_MESSAGES
      - FILTER_BAD_WORDS
      - FILTER_INVITES
      - FILTER_URLS
      - FILTER_ZALGO
      - FILTER_ASCII
      options:
        hide issuer: false
        timestamp: false

With the above configuration, this will send all of the automoderators to that defined channel. As none of these contain any issuer data, the hide issuer setting will not do anything.

If you require more help with setting this up, please ask for support on the SajuukBot discord support server.

Event Names

Please find below all the event names for multi-modlogs. They are case sensitive and must be entered as given or they will not do anything.

Auto Moderator

• CENSOR_BAD_WORDS

• CENSOR_INVITES

• CENSOR_URLS

• CENSOR_ZALGO

• CENSOR_ASCII

• FILTER_EMOJI

• FILTER_ATTACHMENTS

• FILTER_MENTIONS

• FILTER_NEWLINES

• FILTER_DUPLICATES

• FILTER_MESSAGES

• HEURISTIC_DUPLICATES

• HEURISTIC_FLOODING

• HEURISTIC_ATTACHMENTS

• HEURISTIC_MENTIONS

• HEURISTIC_NEWLINES

• HEURISTIC_LINKS

• RAID_FILTER_NEW_ACCOUNTS

• RAID_FILTER_JOINS

• RAID_FILTER_MESSAGES

Base Guild Changes

• GUILD_NAME_CHANGE

• GUILD_OWNERSHIP_CHANGE

• GUILD_VERIFICATION_CHANGE

• GUILD_INVITE_CREATE

• GUILD_INVITE_DELETE

Guild Channel and Role Changes

• CHANNEL_CREATE

• CHANNEL_UPDATE

• CHANNEL_DELETE

• CHANNEL_SLOWMODE

• ROLE_CREATE

• ROLE_UPDATE

• ROLE_DELETE

Moderation

• CHANNEL_CLEAN

• CHANNEL_LOCK

• MEMBER_WARN

• MEMBER_TEMPMUTE

• MEMBER_KICK

• MEMBER_TEMPBAN

• MEMBER_SOFTBAN

• MEMBER_BAN

• MEMBER_BAN_BY_NAME

• MEMBER_UNBAN

• MEMBER_UNMUTE

• MEMBER_MUTE

• MEMBER_VOICE_DISCONNECT

• MOD_BAN_CHANGE

• MOD_MUTE_CHANGE

• MOD_TEMPROLE_CHANGE

• MEMBER_MULTI_WARN

• MEMBER_MULTI_KICK

• MEMBER_MULTI_BAN

• MEMBER_MULTI_MUTE

Other Events

• MESSAGE_EDIT

• MESSAGE_DELETE

• MEMBER_JOIN

• MEMBER_JOIN_RESTORE

• MEMBER_LEAVE

• MEMBER_USERNAME

• MEMBER_NICKNAME

• MEMBER_ROLE_CHANGE