The Moderator module is the central hub for configuring how Discortics handles rule enforcement, case logging, and automated moderation (Autopilot) within your server.
1. Case Tracking
The Case Tracking section tells the bot where and how to log moderation actions.
- Modlog Channel: Select a channel where the bot will post a detailed embed for every moderation action (warn, mute, kick, ban, etc.). This acts as your server's permanent audit trail.
- Muted Role: Choose the role the bot should assign when a user is muted via command or Autopilot. Ensure this role is properly configured in your channel permissions to prevent the user from sending messages.
- Member Role: Select the base role given to users (if applicable). This is primarily used for lockdown commands to revoke and restore channel access for general members.
- Case Count: Displays the total number of moderation cases recorded in your server's history.
Image PlaceholderDescription: A screenshot of the Case Tracking section, highlighting the Modlog Channel and Muted Role dropdown menus.
2. DM Notices
The DM Notices panel allows you to decide whether the bot should attempt to send a Direct Message to users when a moderator takes action against them.
You can individually toggle DM notifications for:
- Warns
- Mutes (Timeouts)
- Kicks
- Bans
Note: If a user has their DMs closed, or shares no other servers with the bot, the DM will fail, but the moderation action will still be successfully applied and logged.
3. Autopilot (Automated Moderation)
The Autopilot system acts as your 24/7 automated security guard. Discortics syncs with Discord's native AutoMod where possible to ensure instantaneous filtering.
General Settings
- Log Channel: Designate a specific channel where Autopilot detections are logged (this can be the same as your main Modlog, or a dedicated
#automod-logschannel). - Log Events: Toggle whether you want Autopilot to send logs at all.
Configuring Modules
Click on the different Autopilot module tabs (e.g., Profanity, Anti-Mention) to configure specific filters.
Profanity Filter
- Presets: Quickly block common bad words using Discord's official AutoMod wordsets (like Severe Profanity or Slurs).
- Allowlist: Add specific words here that you don't want the filter to catch. This is useful for false positives.
Anti-Mention Filter
- Limits: Set strict limits on how many total mentions, user mentions, role mentions, or channel mentions a single message can contain.
- Mention Raid Protection: Enable this to automatically detect and handle bot-coordinated mention raids.
- Allow @everyone: Toggle whether regular users are allowed to try and ping
@everyone(even if they lack the discord permissions to actually ping it, the attempt can still be filtered).
Image PlaceholderDescription: A screenshot of the Autopilot configuration panel, showing the Profanity Presets and Anti-Mention limits.
Frequently Asked Questions (FAQ)
Q: Does Discortics replace Discord's built-in AutoMod?
A: No, Discortics actually works with Discord's AutoMod! For filters like Profanity, Discortics pushes your settings directly into Discord's native system for the fastest possible response, while providing enhanced logging and dashboard management.
Q: Why isn't the Muted role working?
A: If a user is muted but can still talk, check your channel permissions. The Muted role must be set to explicitly Deny the "Send Messages" permission in the channels where you want them silenced. Also, if your server uses Discord's native Timeout feature, the role might not be strictly necessary, but serves as a great visual indicator.
Q: A moderator banned someone but it didn't show up in the Modlog. Why?
A: Ensure the bot has the "View Channel" and "Send Messages" permissions in the designated Modlog channel. Additionally, if the moderator used Discord's native right-click ban instead of the Discortics /ban command, it might bypass the bot's case generator unless native logging is enabled.