Security & Channel Locks

Raid mode, channel locks, slowmode and bulk message clearing for when things go wrong.

When things go wrong

These are the tools you reach for during an incident, not settings you configure once.

• /lock and /unlock — stop everyone talking in a channel. The first thing to do when a raid or an argument is in progress: lock, then deal with it. Pass channel to lock somewhere you aren't, and duration to have it reopen on its own.
• /slowmode — throttle a channel instead of closing it. Better than a lock when a channel is merely too fast, like during an event.
• /serverlock on — close the whole server at once, with an optional duration so it lifts itself. /serverlock off restores every permission to exactly what it was before.
• /clear — bulk-delete messages. Purges are logged to your Mod Log with who ran them and what was removed.

Before you need them

Decide now which channel you lock first and who has permission to do it. During an actual raid nobody reads documentation.

Automated protection lives on the dashboard Security tab: anti-raid for join bursts, and anti-nuke for a compromised or rogue admin (mass channel/role deletes, bans, kicks, webhooks, or granting Administrator — Cyndrix strips their roles, optionally bans, and can ping staff). The server owner and Cyndrix are always exempt. Verification is the standing gate for new accounts. /serverlock is the manual lockdown.

A server lock closes channels that explicitly allow @everyone to talk, not just the role default — so a channel deliberately opened inside a locked category is closed too. Staff roles with their own permission keep talking. Timed locks are stored, so restarting the bot mid-lock still lifts it on schedule.

Commands 5

Generated from the bot's source — this list is always what is actually deployed.

Related