Documentation

Config: Limit 7, Mute After 2. A raid bot joins and sends 10 messages in 3 seconds. The 8th message is deleted, the bot's counter hits 1. It sends 7 more — the bot exceeds the limit again, counter hits 2 which equals Mute After, so it receives a 10-minute timeout.

The bot is silenced automatically without any moderator needing to intervene.

Limit 6, Mute After 2 — tight enough to catch raid bots but permissive enough for normal fast conversation. Add bot channels to Whitelisted Channels if you have game bots that respond quickly.

A member posts https://example-casino.com/join?ref=123 in #general. Anti-Links detects the external URL, deletes the message, and increments their violation counter. They try again — message deleted, counter hits 2 (Mute After), 10-minute timeout applied.

Add your community's frequently shared domains to Whitelisted Links (e.g. youtube.com, twitch.tv). Give trusted content-creator roles to Whitelisted Roles. Set a dedicated #links channel in Whitelisted Channels as a safe place to share URLs.

A user posts discord.gg/rival-server in #general. The invite link is deleted instantly. If they do it again, they receive a timeout. Your partnerships team can freely share invites in #partnerships since it's whitelisted.

Enable: Yes on all public servers. Invite advertising is one of the most common minor rule violations.
Mute After: 2 — standard. Users who post invites twice in quick succession are clearly not doing it by accident.
Whitelisted Channels: Add a #partnerships or #self-promo channel if your community allows server sharing in a designated area.
Whitelisted Roles: Add a @Partner or @Verified Partner role so approved partner servers can share their invite without being flagged.

Config: Mention Limit 5. A user sends "@user1 @user2 @user3 @user4 @user5 @user6 you're all losers". That's 6 mentions, which exceeds the limit — message deleted, violation recorded. They try twice more — timed out after the second.

Set Mention Limit to 4–5. Whitelist your #announcements channel if staff legitimately mention many users in posts.

Config: Threshold 70%. A user sends "STOP IGNORING ME THIS IS RIDICULOUS" — 100% caps, deleted. They send "Hello everyone HOW ARE YOU doing" — roughly 40% caps, allowed through. They send "HELLO how ARE YOU" — about 65% caps, allowed (under threshold).

Threshold: 70% (default) works well for most servers. Lower to 60% if you have frequent shouting issues; raise to 80% for casual gaming servers where caps are more common in excitement.
Mute After: 2 — gives users one clear deletion warning before a timeout is applied.
Whitelisted Channels: Whitelist #games, #memes, or #hype channels where ALL-CAPS messages are culturally normal (celebrating a win, hype posts, etc.).
Tip: Enable Auto-Warn for Anti-Caps only if you run a strict community — on casual servers, accidental caps violations will quickly inflate warning counts.

Warn System config: Auto-Ban at 5 warnings. Auto-Warn enabled for Anti-Spam.

Day 1: User spams 3 times → 3 Auto-Warn warnings issued → counter: 3. They post a blacklisted word (Auto-Warn on) → counter: 4. They spam again → counter: 5. Auto-ban fires — the user is permanently banned without any moderator action.

Always enable for: Anti-Spam, Anti-Links, Anti-Discord, Word Blacklist — these are the most deliberate violations and warnings are appropriate.
Consider enabling for: Anti-Mention, Anti-Selfbot — targeted harassment and ToS violations deserve a warning trail.
Use caution with: Anti-Caps and Ghost Ping — casual servers may see too many accidental warnings from these. Only enable if you run a strict community.
Pair with the Warn System: Set Auto-Kick at 5 and Auto-Ban at 8. This creates a full escalation chain: violation → warning → accumulate → kick → ban, entirely automatic.

User A pings @User B to annoy them, then immediately deletes the message. User B gets a notification but sees nothing. The bot detects the deleted mention and posts: "⚠️ Ghost ping by User A — mentioned: @User B" in the channel. Moderators can now see it and act. With Auto-Warn enabled, User A also receives a warning.

Enable: Yes on any server that has issues with trolling or harassment — ghost pinging has no legitimate use.
Whitelisted Channels: Whitelist #bot-commands or #testing if bots in those channels trigger ghost-ping patterns inadvertently.
Auto-Warn: Enable — persistent ghost pingers accumulate warnings naturally toward your Warn System thresholds.
Note: The alert is posted in the same channel the ghost ping happened in, making the behaviour publicly visible. This deters repeat attempts without requiring mod intervention.

Create a Verified role. Set all your server channels to be visible only to members with that role. New members land in a #verify channel (visible to everyone), click the button, receive the Verified role, and immediately see the rest of the server. Bots and raid accounts that cannot click buttons never get access.

You add free nitro, discord gift, and a list of slurs to the blacklist. A scam bot joins and posts "claim your FREE NITRO here: scam.com" — the phrase free nitro matches (case-insensitive) and the message is deleted instantly, before any member sees it.

Start with these phrases: free nitro, discord gift, steam gift card, bit.ly (shortener used in scams), your server's known competitor names if advertising is an issue.
Add community-specific terms: Slurs, harassment language, and any words your moderation team repeatedly has to delete manually.
Whitelisted Channels: If mods need to discuss blacklisted terms (e.g. reviewing reports), whitelist your #mod-discussion channel so staff can paste evidence without it being auto-deleted.
Whitelisted Roles: Add your @Moderator role so mods can quote rule-breaking messages in their reports without triggering the filter.
Auto-Warn: Enable — deliberate use of blacklisted words is worth recording as a warning for repeat pattern detection.

Config: Minimum Age 7 days, Action: Kick, Send DM: on. During a raid, 15 accounts all created in the last 2 hours try to join. Each one is kicked on arrival before they can type a single message. Each receives a DM: "Your account is too new to join this server. Please wait 7 days after account creation and try again."

Use 7 days + Kick for most servers. Switch to 30 days + Kick for gaming/community servers that are frequently targeted. Avoid Ban unless you are certain you don't want those users back ever.

A user running a selfbot script sends a message with a custom rich embed (title, description, colour fields) from their personal account. Since regular Discord clients cannot send embeds from user accounts, Anti-Selfbot flags this immediately — the message is deleted and (if Auto-Warn is on) a warning is issued.

Enable: Yes on any public server. Selfbots are a ToS violation and are commonly used for harassment, mass-DM spam, and account farming.
Whitelisted Channels: None typically needed. Rich embeds from user accounts are always suspicious.
Whitelisted Roles: If you have a developer role for users testing legitimate Discord integrations (e.g. webhook tools that mimic embed-like messages), add that role to avoid false positives.
Auto-Warn: Enable — selfbot use is a deliberate violation. A single warning on detection often causes the user to stop immediately. If they continue, the warn ladder handles escalation automatically.

Warning 3 → Assign "Warned" role (visible to mods, signals repeat offender)
Warning 5 → Auto-kick (removed, can rejoin with a clean slate)
Warning 8 → Auto-ban (persistent rule-breakers removed permanently)

With Auto-Warn enabled on Anti-Spam and Anti-Links, members who repeatedly break rules accumulate warnings automatically and hit these thresholds without requiring manual mod intervention.

A compromised moderator account adds the @Owner role to an attacker. That role has Administrator permission. Security Sweep fires immediately: "Security Alert: Admin Permission Granted — [Attacker] was granted ADMINISTRATOR. Granted by: [Compromised Mod]". Your security team is pinged. You can revoke the role and investigate before any damage is done.

A new member joins, and minutes later someone adds the @Admin role to them. Security Sweep fires the Admin Granted alert with an extra warning field: "⚠️ This user received ADMINISTRATOR within 24 hours of joining!" This catches social-engineering attacks where an attacker joins, builds quick trust, and gets elevated fast.

You track @Head Moderator as a Critical Role. Any time someone is added to or removed from that role — even by a legitimate admin — an alert fires: "Security Alert: Critical Role Change Detected — [User] | Roles Added: @Head Moderator | Changed By: [Admin]". This creates a full audit trail for your highest-trust staff positions.

Log channel: Create a private #security-alerts channel visible only to server owners and senior staff. Set this as the Security Sweep channel.

Mention Roles: Add your @Owner and @Head Admin roles so the right people are pinged immediately on any alert.

Critical Roles to track: Add every role that has Administrator, Manage Server, Manage Roles, or Ban Members permissions — @Admin, @Head Moderator, @Co-Owner, etc. Any change to these roles on any member will generate a logged, pinged alert.

Works best alongside: Anti-Nuke (blocks mass privilege abuse) + Logging (records all moderation actions). Security Sweep fills the gap by catching single, targeted privilege escalations that Anti-Nuke thresholds might not fire on.

Config: Threshold 3, Auto Action: Ban. A user scammed members in three separate servers — all three servers banned and reported them to the network. When they try to join your server, the bot sees they have 3 reports (meeting your threshold) and bans them before they send a single message, even though they've never been in your server before.

Start with Flag + Threshold 3. Review flagged users manually for a week to get comfortable before switching to automatic Kick or Ban. Raise threshold to 5 if you see false positives.

Your Head Mod reorganizes the server by deleting 4 old channels and creating 5 new ones. Without a whitelist, Anti-Delete Channel and Anti-Create Channel would both trigger and punish them. With their Head Mod role in Global Whitelisted Roles, all of their actions pass through freely. If Log Whitelisted Actions is on, each deletion and creation still posts to your alert channel as a whitelisted event — so you have a full audit trail without false punishments.

Add your Admin and Head Mod roles to Global Whitelisted Roles. Add any trusted bots' user IDs to Global Whitelisted Users. Enable Log Whitelisted Actions so you can verify their behaviour is expected. Enable the master switch only after your whitelist is configured.

Your Head Admin deletes 10 channels during a restructure. Their role is in the Global Whitelist. Those 10 deletions are not counted as violations — the day count for Anti-Delete Channel stays at 0 for them. A separate compromised account who deletes 3 channels (with /Day: 2) would still hit Phase 1 immediately because their count is tracked independently.

A legitimate admin was setting up new channels quickly and triggered Anti-Create Channel (their daily count hit 3, exceeding the /Day: 2 limit). Phase 1 fired and stripped their roles. Open the Violation Monitor → reset their count → manually restore their roles. Then add their role to the module's whitelist so it never happens again during setup work.

Same setup, but ModUser's role is in the global whitelist. The flow runs through Steps 1–5, hits the global whitelist check at Step 5 and finds a match. No violation is recorded. No punishment is applied. If Log Whitelisted Actions is on, an embed still fires in the alert channel: "ℹ️ Whitelisted action — Anti-Delete Channel | Actor: ModUser#1234 | Action: Deleted #general | No punishment (whitelisted)." The event is auditable, but the mod is never punished.

Category 1: Label: "General Support" | Emoji: 🎫 | Access Roles: @Support Team | Channel: ticket-{count}-{member} | Welcome: "Hey {user}! A support agent will be with you shortly."

Category 2: Label: "Bug Report" | Emoji: 🐛 | Access Roles: @Developers | Channel: bug-{count} | Welcome: "Thanks for the report {user}! Please describe the bug and include steps to reproduce."

Category 3: Label: "Partnership" | Emoji: 🤝 | Access Roles: @Partnership Team | Channel: partner-{count} | Welcome: "Hi {user}! Tell us about your server."

Each category creates tickets in its own Discord category, visible only to the opener and the relevant team role.

Discord category per ticket type: Create a separate Discord channel category for each ticket type (e.g. "Support Tickets", "Bug Reports", "Partnerships"). Set each Menu Ticket category to that Discord category so tickets are organised by type automatically.
Access Roles — keep them separate: Your @Support Team should not see Bug Report tickets, and your @Developers should not see general support tickets. Assign the most specific role possible to each category.
Channel name template: Use ticket-{count}-{member} for support tickets (e.g. ticket-42-john). Use bug-{count} for bug reports where the member name is less important.
Welcome message: Front-load information collection. Instead of "an agent will assist you", say "Hey {user}! Please describe your issue and include: 1) what happened 2) what you expected 3) any screenshots." This cuts response time significantly.
Max categories: Start with 3–5 categories. More than 8 makes the dropdown feel overwhelming to users. Combine similar topics (e.g. merge "Question" and "Help" into "General Support").

An attacker deleted 8 channels before Anti-Delete Channel fired and banned them. Anti-Nuke stopped the attack but the 8 channels are still gone. You go to the Backups panel, find the backup from 36 hours ago (before the attack), and restore it. All 8 channels are recreated with their original settings and permission overwrites.

Enable Auto-Backup alongside Anti-Nuke. Anti-Nuke stops attacks in real time — Auto-Backup ensures that even if something slips through, you have a recent snapshot to restore from. Also create a manual backup before any major server restructure.

Create a private #audit-log category visible only to admins. Set up four channels: #audit-log, #mod-actions, #reports, #boosts — one per log type. This keeps your admin overview clean and each type of event easy to find when you need to investigate something.

Channel access: Restrict all log channels to @Admin and @Head Moderator only. Never give lower-rank mods access to audit logs — they contain full action history including disciplinary records.
Audit Log: Always enable. This is your primary record of member joins, leaves, message deletions, and role changes — essential for investigations.
Admin Command Log: Enable alongside Audit Log. When a member asks "why was I warned?", this log shows which moderator issued the action and when.
Report Log: Enable if you use the bot's /report command. Route it to a separate #reports channel so reports don't get buried in general audit events.
Boost Log: Enable and route to a semi-public channel like #server-updates so staff (and optionally members) can celebrate new boosters.