Raid and nuke protection
If too many people join in a short time, CodeBot alerts the staff, locks the channels or kicks the newcomers. Anyone who mass-deletes channels and roles or mass-bans, unless they own the server, is stopped. Take a backup first: if something goes wrong you can put back what is missing.
-
Turn on raid protection
Choose how many joins in how many seconds count as a raid, and what happens: only alert the staff, lock every text channel, or kick everyone who joins.
/security raid enabled:True joins:10 joins seconds:10 seconds action:lock every text channel -
Stop brand-new accounts
Accounts newer than the days you choose are kicked when they join; this cuts off raids made with fresh accounts.
/security age days:7 days -
Turn on nuke protection
Whoever deletes or bans a lot in a short time is stopped. Add the staff you trust to the trusted list.
/security nuke enabled:True -
Take a backup
Roles, channels and permissions are saved. Automatic backups run every day; with 💎 Premium every hour (24 kept).
/backup auto enabled:True -
Check the status
See which protections are on, on one screen.
/security status
Commands in this guide
Every option is on the commands page.
Questions people ask
Do the channels open again after a raid?
Yes, they open on their own when the time you chose is up. To end it now use /security end.
More guides
- Setting up registration Newcomers wait with an unregistered role; staff register them with a name and age.
- A ticket system A panel with buttons, a private channel per ticket, a transcript when it closes.
- Application forms (staff recruiting) Write your questions, get applications in a review channel, accept with one click.
- Automatic punishments with penalty points Warnings add up points, and a step punishes on its own when it is reached.