Moderation & Security
NexaBot's moderation stack is made of three layered systems: AutoMod for day-to-day rule enforcement, anti-raid for mass-join events, and anti-nuke for abusive admin-level actions.
AutoMod & warn ladders
AutoMod watches for rule violations and escalates automatically using a warn ladder — a configurable sequence of consequences that gets more severe the more times a member breaks the rules. A typical ladder might look like:
| Offense | Consequence |
|---|---|
| 1st | Warning logged, member notified |
| 2nd | Timeout |
| 3rd | Kick |
| 4th+ | Ban |
The exact thresholds and consequences are configurable per server in the Nexa Dashboard.
Anti-raid
Anti-raid looks for patterns typical of a coordinated raid — a burst of new member joins in a short window — and can automatically slow down or lock joining until the activity is reviewed.
Anti-nuke
Anti-nuke protects against a compromised or malicious admin account causing mass damage: bulk channel deletion, bulk role deletion, or bulk bans in a short period. When triggered, it can strip the acting account's dangerous permissions and alert server staff.
Staff command abuse tracking
NexaBot also tracks patterns of command usage by staff members themselves, flagging unusual spikes (for example, a moderator issuing an unusually high number of bans in a short window) so server owners can review it.
Configure thresholds deliberately
Anti-raid and anti-nuke thresholds that are too sensitive can flag legitimate activity (an active event, a large partner raid welcome). Start with the setup wizard's defaults and adjust gradually.
Case history
Every moderation action — warns, timeouts, kicks, bans — is logged to a per-member case history, viewable from the mod-log channel or the Dashboard.