Discord Anti-Raid Setup Checklist for Growing Communities

Use Discord's native safety controls first

Discord's official raid-protection guide recommends restricting broad mention permissions, enabling Raid Protection alerts where available, setting an appropriate verification level, configuring AutoMod, and preparing trusted moderators. These controls should remain active even when a third-party bot adds another layer of defense.

• Disable @everyone, @here, and broad role mentions for normal members.
• Set verification requirements appropriate for a public server.
• Configure AutoMod mention-spam and keyword rules.
• Choose a private alert channel that active moderators can see.
• Confirm staff know how to pause invites and apply slowmode during an incident.

Add Trinix account-age screening carefully

Trinix provides /autokick_toggle and /autokick_threshold for suspicious-join screening based on account age. Choose a threshold that reflects how members actually discover the server. An aggressive setting can block legitimate new Discord users, event attendees, customers, or students.

Use /autokick_whitelist and /autokick_unwhitelist for documented exceptions. Keep the whitelist narrow and review it after events or partnerships end.

Prepare the staff response before the raid

A raid plan should identify who can pause invites, lock channels, adjust verification, review new members, remove attackers, and communicate with the community. Avoid giving every moderator full administrator access. Discord's roles and permissions guidance is the right reference when designing staff access.

Run a tabletop exercise with a private test channel. Confirm that the bot role can perform approved actions, that staff can reach the log channel, and that an owner can recover if a role is misconfigured.

What to do during an active incident

1. Pause new invites or raise the verification level if joins are still arriving.
2. Enable slowmode or lock the most affected channels.
3. Reduce mention-spam limits and add current raid phrases to AutoMod.
4. Use Trinix logs to identify the affected channels, accounts, and invite patterns.
5. Use /masskick only after validating the target criteria and confirming that protected users will not be included.
6. Preserve enough evidence for staff review before deleting the incident trail.

High-impact commands should never be improvised under pressure. Limit access, confirm the selection, and have a second staff member review the action when the server size permits.

Recover without punishing normal members

Once activity stabilizes, reopen channels in stages. Review removed accounts, warning records, role changes, and invite activity. Tell members what controls changed and when temporary restrictions will be removed. Do not publish private log content or personal information as part of the announcement.

Update the written incident plan while the details are fresh. If a threshold caused legitimate members to be removed, correct the setting and document the exception process.

Anti-raid readiness checklist

• Native Discord verification, AutoMod, and alert settings reviewed.
• Broad mention permissions restricted.
• Trinix logger tested in a private channel.
• Account-age threshold validated against real join patterns.
• Whitelist ownership assigned to named staff.
• Emergency roles and high-impact commands limited.
• Pause-invite, slowmode, lock, and recovery steps documented.

For the Trinix side of the configuration, see the AI moderation guide and command documentation.