Automoderation stops harmful messages and suspicious joins before staff need to react. The Discord commands use the name Autopilot, and each protection has its own settings and punishment policy.
Start with the problem your server actually has. Enable one protection, test it with a non-administrator account, then add another.
Choose a protection
- Profanity: block profanity, sexual content, and slurs.
- Mentions: stop mass user, role, channel,
@everyone, and@herementions. - Spam: stop duplicate messages and rapid message bursts.
- Honeypot: create a warning channel that catches automated scam posts.
- Links: block invites, phishing, short, adult, and custom domains.
- Flood: remove text walls, emoji floods, and repeated content.
- Anti-Raid: detect suspicious joins and risky new accounts.
Turn on one protection
Enable from the DashboardUse one protection first so false positives are easy to identify.
- Open Dashboard → Moderator → Autopilot.
- Choose one protection.
- Enable it and review its detection settings.
- Choose its punishment.
- Add only the trusted roles or channels that need an exception.
- Save and run a harmless test.
[Insert screenshot here]
One enabled protection in Dashboard → Moderator → Autopilot
Before you begin
- You need Administrator to use the Autopilot setup commands.
- Discortics needs Manage Messages to remove violations.
- Mute, Timeout, Kick, and Ban need their matching Discord permissions.
- Keep the Discortics role above members and roles it may moderate.
- Configure the server muted role before selecting Mute.
- Administrators are skipped by message protections, so use a non-administrator test account.
Every protection starts disabled. Opening its settings does not enable it.
Punishments
Profanity, Mentions, Spam, Links, and Flood each have a separate punishment policy.
- Warn creates a warning case when enabled and no stronger punishment takes precedence, and posts a notice in the triggering channel.
- Mute, Timeout, Kick, and Ban can run after a chosen number of detected offenses inside a time window.
- Mute, Timeout, and temporary Ban also use a duration.
- Notifications control whether Discortics tries to DM the member.
Channel warning notices work independently of the DM switch. During a burst, notices are limited to one per member, protection and channel every ten seconds. Join-only checks have no triggering channel.
Offenses are counted separately for each protection even when Warn is disabled. Spam offenses do not count toward a Link threshold.
Exceptions and limits
| Resource | Public | Prime | Custom |
|---|---|---|---|
| Ignored users per protection | 7 | 15 | 25 |
| Ignored roles per protection | 7 | 15 | 25 |
| Ignored channels per protection | 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 |
Not every protection supports every exception type. Each child guide lists the exceptions available for that protection.
Reset a protection
Run the matching Autopilot command, select Reset, review the confirmation, then select Yes, Reset.
Warning: Reset removes that protection's custom detection values, ignored lists, allowlists, and punishments. It cannot be undone automatically.
Resetting one protection does not change another.
Common problems
A test message is ignored
Test from a non-administrator account. Confirm the protection is enabled and the user, role, and channel are not ignored.
A message is removed but no punishment runs
Confirm Warn is enabled and Discortics has the permissions and role position required for the selected action.
The Discord panel stopped responding
Autopilot panels expire after five minutes. Run the same command again.
Autopilot action logs and AntiRaid incident alerts use the modlog channel configured with /settings moderation. Autopilot panels show a setup warning if this channel is missing.