NightsNights
Terms of ServicePrivacy PolicyAvatar HistoryTickets
CommandsDocsBuySupportAdd to Discord
NightsNights

A premium Discord bot for moderation, voice, music and support — built for communities that outgrow everything else.

Add to Discord

Navigate

  • home
  • commands
  • docs
  • support
  • invite

Legal

  • Terms of Service
  • Privacy Policy
  • Tickets

© 2026 Nights. All rights reserved.

discord.gg/scares

Introduction

  • Overview
  • Getting started
  • Permissions

Safety

  • Moderation
  • Antinuke

Features

  • VoiceMaster
  • Music
  • Tickets
  • Starboard
  1. Docs
  2. Safety
  3. Antinuke

Antinuke

Threshold-based protection against mass bans, channel deletion and rogue bots.

Antinuke watches destructive actions and counts them per actor. When someone crosses a threshold inside the tracked window, Nights applies the punishment you configured — automatically, without waiting for a human.

Enable this before handing out staff roles

Antinuke cannot undo damage that happened before it was switched on. Turn it on first, then promote people.

Enable the system#

Antinuke is off by default. Enabling it is a single command, but note that it is gated on the antinuke admin role rather than a Discord permission — see permissions.

,an enable
,antinuke
,antinukeantinuke admin

Show the antinuke overview and current status. Aliased to ,an.

,an enableantinuke admin

Enable the antinuke system.

,antinuke disableantinuke admin

Disable the antinuke system entirely.

Configure each module#

Modules are configured independently, so you can be strict about bans and relaxed about channel edits. Each takes an action and a threshold.

,an ban on --do ban --threshold 3
,an botadd on --do ban
,an channel on --do strip --threshold 5
ParameterTypeDescription
on | offrequiredstateWhether this module is actively watched.
--doban | kick | stripWhat happens to an actor who crosses the threshold. strip removes their roles instead of removing them.
--thresholdnumberHow many actions inside the tracked window before the punishment fires. Lower is stricter.

Bot additions have no useful threshold

A single unauthorized bot is already the whole attack, so ,an botadd is normally left without a threshold — it acts on the first occurrence.

Allowlisting#

Legitimate automation will trip these modules. Authorize the accounts that are meant to perform bulk actions so they are exempt:

  • Bots you deliberately added — logging, levelling, backup tooling.
  • Staff accounts that run scheduled cleanups.
  • The server owner, who is always exempt and cannot be actioned by antinuke.
,antinuke permissions grant @Lupos
,antinuke admin list

Verify before you rely on it

Run ,antinuke after configuring. The overview lists every module with its current state, action and threshold — if a module reads as disabled there, it is not protecting you.

Still stuck?

Ask in the support server — a human will get back to you.

Get support
PreviousModerationNextVoiceMaster