DISCON Experiment
DISCON is your server's danger level, modeled on DEFCON. During a raid, your team no longer has to open /settings to change Discord's verification, enable the captcha and close DMs one by one: one click on the DISCON panel, and we apply all the protections of the chosen level at once. A second click, and we undo what we had enabled.
❓ How does it work?
- Five levels: from level 5 (calm) to level 1 (catastrophe). The lower the level, the stricter the protection.
- A panel for the team: a message posted in a staff-only channel, with one button per level. One click is enough to change level.
- Effects calculated for your server: what a level does depends on your configuration (captcha configured or not, Community mode, Auto RaidMode action). The scale shown in the configuration and on the panel describes exactly what will happen on your server.
- A clean return: when going back down, we only turn off what DISCON itself enabled. A captcha, a DM Lock or a raid mode that you enabled by hand stay in place.
- A manual change: the level never changes by itself, your team decides.
DISCON is part of the Shield Update, planned for version 3.6.0. Until its release, it is an experiment, in public beta for Premium servers. The status voice channel requires Premium.
🚦 The five levels
| Level | Name | What we apply |
|---|---|---|
| 🔵 DISCON 5 | All is well | Medium Discord verification, nothing else. This is the default level. |
| 🟢 DISCON 4 | Vigilance | Captcha enabled if configured (channel and role). Without a captcha, high Discord verification instead. |
| 🟡 DISCON 3 | Alert | Highest Discord verification, captcha enabled if configured, DM Lock. The captcha applies to all newcomers. |
| 🔴 DISCON 2 | Critical | Everything from level 3, plus the frozen captcha: no one gets in. Without a captcha, we enable raid mode instead. |
| ⚪ DISCON 1 | Catastrophe | Everything from level 2, plus the lockdown: @everyone can no longer write, react, speak in voice or use commands. |
Discord verification
Each level sets your server's Discord verification level: medium at levels 5 and 4 (high at level 4 if the captcha is not configured), highest from level 3 to level 1.
Entry captcha and frozen captcha
- Level 4: we enable the captcha if it is configured, even if you had disabled it, without touching its channel or role. It then follows your trigger setting: on Automatic, it still applies to no one outside a raid.
- Level 3: the captcha applies to all newcomers, whatever its trigger (see priority over triggers).
- Levels 2 and 1: we switch the captcha to Panel mode and freeze it. Newcomers receive the verification role and wait behind the door: they cannot solve the challenge while the level holds. Once the level goes back up, they pass the captcha normally, without having to join again. When going back down, we give the captcha back the display mode it had before.
DM Lock
From level 3, we enable the DM Lock: DMs are how scams get through when the server closes. It requires Community mode and the "Manage Server" permission for RaidProtect. Without these prerequisites, the level still applies and a warning tells you DM blocking could not be enabled.
Level 1 lockdown
At level 1, we remove the speaking permissions from the @everyone role: send messages (including in threads), add reactions, create threads, send voice messages, attach files, speak in voice and use application commands. They are restored exactly as they were when going back down.
🧩 Prerequisites for levels 2 and 1
For levels 2 and 1 to really hold newcomers at the door, one of these two conditions must be met:
- A configured captcha (verification channel and role): this is the recommended solution. The frozen captcha holds everyone, then lets legitimate members in once calm returns. Configure the captcha.
- Otherwise, the Auto RaidMode action set to "Kick everyone arriving": without a captcha, we enable raid mode, and its action decides the fate of newcomers. With the "Lock invites" action (default setting), the raid mode opened by DISCON kicks no one. Set it in the Auto RaidMode configuration.
The level 1 lockdown also requires that RaidProtect can edit the @everyone role ("Manage Roles" permission). If it cannot, a warning tells you.