Anti-raid
Lock down your community the moment joins, messages or invites spike beyond normal levels.
Set the protection level
Choose OFF, LOW or HIGH under Configuration, Anti-raid, or run n!antiraid <low | high | off> from chat. The level is a server-wide alert state that on its own does nothing: its power comes from automod rules. A rule gated to LOW runs while the level is LOW or HIGH, a rule gated to HIGH runs only at HIGH, and ungated rules always run, so escalating the level arms stricter rules. Rules raise and clear the level automatically during an attack, so in day-to-day use you leave it OFF; whichever way it is set, it stays until something changes it again.
Machine Learning Anti-Raid
Every server is equipped with the Machine Learning Anti-Raid system on the Automod page. Nighthawk evaluates incoming join patterns and account signals in real time to detect coordinated raid waves before raiders can flood your channels. When a raid is detected, Nighthawk neutralizes the attacking cluster in parallel, escalates your server alert level to HIGH, and syncs confirmed threat accounts to the Global Watchlist.
Tune threat sensitivity and logging
Under Configuration, Anti-raid, select your detection sensitivity (Medium recommended, High during active waves, Low for large public events) and mitigation action (Massban Cluster, Kick, Quarantine, or Staff Alert Only). You can also bind an Anti-raid logging category under Configuration, Log channels to receive forensic reports.
Automated escalation and alerts
The set anti-raid level action lets a rule raise or clear the level on its own, which is what gives you hands-free protection during a sudden raid. Pick one or more Alert roles under Configuration, Anti-raid and Nighthawk pings them in your alerts channel whenever a rule raises the level. Clearing the level is posted without a ping.
Sweep a whole join burst
Punishments normally hit only the member whose join crossed the threshold. Switch on Sweep in a join-spam rule and Nighthawk applies the rule’s warn, mute, kick and ban actions to everyone who joined inside the triggering window instead. Bots, Nighthawk itself and members exempt from the rule are always skipped, and the alert, reply and level change still fire only once. Raid Guard (High) ships with sweep on, which is how the chain clears a whole raid wave once the level reaches HIGH.
Manual lockdown
Use n!lockdown, or the lockdown button on the dashboard Overview page, to instantly lock down the whole server during an active raid: every text channel denies Send Messages for @everyone and the anti-raid level is raised to HIGH. Channels that must stay open for staff communication can be exempted with the lockdown_exempt_channels config key. Lifting it with n!unlock restores the channels and puts the anti-raid level back to whatever it was before.
Return to normal
Once the raid passes, set the level back to OFF from the dashboard or with n!antiraid off. You can also let it clear itself: Auto-lower after inactivity takes a number of minutes, and once the server has gone that long without a single join, Nighthawk clears the level and logs it. Leave the field empty to always lower it by hand. The timer lives in memory, so a bot restart starts the countdown over.
Review what happened
The Anti-raid activity card on the dashboard Overview page lists every level change and detected join burst, each with the source that caused it: automod, a command, lockdown, auto-lower or the dashboard. It is the quickest way to check whether a rule fired at the right moment or whether your thresholds are too sensitive.