Each protection has its own settings and punishments. Discord commands use the name Autopilot. Every protection starts off, so turn on one at a time and test it.
Choose a protection
| Protection | What it stops |
|---|---|
| Profanity | Profanity, sexual content, and slurs |
| Mentions | Mass user, role, channel, @everyone, and @here mentions |
| Spam | Duplicate messages and rapid bursts |
| Honeypot | Automated scam accounts |
| Links | Invites, phishing, short links, adult sites, and your domains |
| Flood | Text walls, emoji floods, and repeated content |
| Anti-Raid | Suspicious join bursts and risky new accounts |
| Anti-Nuke | Destructive actions by staff, admins, and bots |
Before you begin
- You need Administrator to use the Autopilot commands.
- Discortics needs Manage Messages to remove violations, plus the matching permission for Mute, Timeout, Kick, or Ban.
- Keep the Discortics role above the members it may moderate.
- Set a muted role before you choose Mute.
- Set a modlog channel with
/settings moderationto receive logs and alerts.
Turn on a protection
Enable from the Dashboard
- Open Dashboard → Moderator.
- Select a protection tab, such as AntiSpam.
- Enable it and review its settings.
- Review its punishment steps.
- Add only the exceptions you need.
- Save, then test from a non-administrator account.
[Insert screenshot here]
An enabled protection on Dashboard → Moderator
Punishments
Profanity, Mentions, Spam, Links, and Flood each have their own steps. A step runs when the previous action reaches its count.
Default steps: Warn on detection → 10-minute Timeout after 3 Warns → Kick after 3 Timeouts → Ban after 2 Kicks.
Rules for your own steps:
- The order is Warn → Mute or Timeout → Kick → Softban → Ban. Each step must be stronger than the last.
- Use each action once. Mute and Timeout are the same level, and nothing can follow Ban.
- You can have up to five steps.
- On the Public bot, every enabled protection needs at least one Timeout, Kick, or Ban.
Good to know:
- Counts reset after 30 days without that action, and when you change the steps. They carry over if a member is kicked and rejoins.
- A continuous spam or flood burst counts as one incident.
- Softban bans, deletes one day of messages, then unbans.
- Notifications control DMs. Warn also posts a notice with its case number in the channel.
- Log events turns off Discord logs for that protection. Punishments and cases continue.
- Durations look like
10s,10m, or1h.
Limits
| Resource | Public | Prime | Custom |
|---|---|---|---|
| Ignored users per protection | 7 | 15 | 25 |
| Ignored roles per protection | 7 | 15 | 25 |
| Ignored channels and categories | 7 | 15 | 25 |
| Profanity allowlist entries | 1,000 | 1,000 | 1,000 |
| Link blacklist entries | 1,000 | 1,000 | 1,000 |
| Link allowlist entries | 1,000 | 1,000 | 1,000 |
Each protection's guide lists which exceptions it supports.
Reset a protection
Run its command, select Reset, then Yes, Reset.
Troubleshooting
A test message is ignored. Test from a non-administrator account. Check that the protection is on and the user, role, and channel aren't ignored.
A message is removed but no punishment runs. Check that a punishment step exists and that Discortics has the permission and role position for it.
A protection turned itself off. Discortics turns off a protection when it's missing a permission it needs, or when a Public bot's steps no longer qualify. The reason appears in your modlog and on the Dashboard. Fix it, review the punishments, and turn it on again.
The Dashboard says settings changed. Another admin saved while you were editing. Reload the page, then save again.
The panel stopped responding. Run the command again.
Prefer one-line commands? See Direct Commands.