Censor

Censor watches every message (and some things that are not messages, like nicknames) and removes content that matches your rules. Violations can warn, and repeat violations can auto-mute.

plugins:
  censor:
    levels:
      0:                       # applies to regular members (level 0)
        filter_invites: true
        filter_zalgo: true
        blocked_words: [scamword]
      50:                      # applies to everyone up to level 50 (mods included)
        blocked_words: [superbadword]
    channels:
      665875009507426304:      # extra rules just for this channel
        filter_domains: true

How rules are scoped

The top level holds two maps of sub-configs: levels and channels (extra rules per channel or category). A levels key is a ceiling: rules under it apply to members at or below that level. Rules under 0 apply only to regular members - trusted members, mods and admins are above them. To also filter staff, put the rules under a higher key like 50 or 100. Each sub-config carries the same filter set; the first matching rule wins.

The filters

• Invites - filter_invites, with guild/vanity whitelists and blacklists (invites_guild_whitelist, invites_whitelist, invites_blacklist) and a per-channel exemption list.
• Domains - filter_domains with domains_whitelist / domains_blacklist. Blocked domains match with or without https://, so a bare bad-site.com is caught too, subdomains included. The allow-list only judges real links (with a scheme), so ordinary text can never trip it. List entries are forgiving: paste a full link (https://bad-site.com/whatever) or just the domain - both mean the same thing, and a www. prefix is ignored.
• Words and tokens - blocked_words (whole words) and blocked_tokens (substring matches - use these to catch n1tro-style respellings of a blocked word). Entries are matched literally, so $5 means a real dollar sign - you never need to escape anything, and a stray symbol can never break your filter. If you want actual regex matching, that lives in two places: a channel rule's text pattern (whitelist_text_regex, on the Channel Rules page - see the Utilities docs) and the AutoMod page's regex patterns, which Discord itself enforces.
• Zalgo - filter_zalgo, plus block_zalgo_nicknames for names.
• Caps - filter_all_caps. It only fires on repetition: a message counts when it carries at least all_caps_min_char_length capitals in a row, and the filter acts after all_caps_min_message_count such messages within all_caps_interval seconds. All three thresholds are editable right next to the toggle on the dashboard's Censor form.
• Mentions / nicknames / hoisting - blocked_mentions, blocked_nicknames, hoist_blacklist.
• Message length - message_char_limit.

Most filters take a *_channel_whitelist to exempt specific channels. A whitelisted channel exempts its threads and forum posts too - the filters themselves also run inside threads, like everywhere else.

Escalation

• warn_on_censor issues a warning infraction alongside the deletion.
• mute_violations auto-mutes after mute_violations_count hits within mute_violations_interval seconds, for mute_violations_duration seconds. All three numbers are editable next to the "Mute repeat offenders" toggle on the dashboard's Censor form.

Anti-raid

The antiraid block goes inside a level, next to that level's filters (plugins.censor.levels.0.antiraid), not at the top of the censor block.

It watches join velocity: count joins within interval seconds starts a lockdown for lockdown_duration seconds. While it is active, every new join receives raid_action - a quarantine role (raidrole), a kick, a ban, or a tempban for raid_action_duration - and notifyrole gets pinged. That ping goes to the first mod log channel subscribed to the Raid detected event, so give one of your log channels that event or the ping has nowhere to go.

The optional shield block pauses server invites and/or member DMs at the Discord level (pause_invites, pause_dms) for the lockdown window, so the influx stops at the source.

You can also drive the lockdown by hand:

• !raid status (or bare !raid) - is a lockdown active, and for how much longer.
• !raid on [duration] - start (or extend) the lockdown manually, for example ahead of a raid you can see forming. New joins receive the configured raid_action exactly as if the detector had tripped, and the shield goes up if configured. Duration defaults to lockdown_duration.
• !raid off - lift the lockdown early and return quarantined members to normal (strips raidrole).

Manual enables and lifts write their own mod log entries naming the moderator, alongside the automatic raid detection events.

Testing your rules

Setup → Filters includes a message simulator: paste a message, pick the channel and the member's level, and it shows exactly which censor rule (if any) would catch it - the same first-hit-wins order the bot uses. Every hit names the exact config key that fired (for example plugins.censor.levels.50.blocked_words), so you can jump straight to that line in your config to change or whitelist it.

Commands

Command	What it does
/antiraid	Inspect, manually enable, or lift the anti-raid lockdown: status / on [duration] / off.

Image-based scams are the Image Scan plugin's job; when its OCR layer is on, text found inside images is run through these same censor lists.