Skip to main content

Overview

Verdict Mode is a separate, hardened protection layer that operates independently from the standard Antinuke system. Unlike regular Antinuke — which checks whitelists before deciding to punish — Verdict Mode operates on a pure threshold basis. If any user crosses the defined action threshold within the configured time window, they are immediately banned. No whitelist bypass, no exceptions. Only the server owner is exempt. Verdict Mode is designed for servers that want an absolute last line of defense against even trusted users going rogue.
Verdict Mode will punish anyone who crosses the threshold, including antinuke admins and whitelisted users. Only the server owner is exempt. Configure thresholds carefully.

How It Works

Every destructive action (ban, kick, channel delete, etc.) is tracked per user within a rolling time window. Once a user’s action count reaches or exceeds the threshold within that window, they are immediately banned — regardless of their whitelist status or role. Example: If the ban threshold is set to 5 with a 15s window, a user who bans 5 members within 15 seconds will be instantly banned. The tracking data is cleared on every bot restart to prevent stale data from causing false positives.

Access Control

The same access rules as Antinuke apply:
  • Server Owner — Full access to all Verdict Mode features
  • Extra Owner — Users designated by the server owner
Use extraowner to manage who can configure Verdict Mode.

Commands

Opens the Verdict Mode control panel to toggle individual protections. Requires Verdict Mode to be enabled first.
,verdict
Aliases: verdictmode
Permissions: Server Owner or Antinuke Admin
Enables the Verdict Mode module, unlocking the control panel and verdict set command. Does not automatically enable any individual protections — you must toggle them manually after enabling.
,verdict on
Permissions: Server Owner or Antinuke Admin
Disables Verdict Mode entirely. All active Verdict protections become inactive immediately.
,verdict off
Permissions: Server Owner or Antinuke Admin
Configure the threshold and time window for a specific action type. Both values must be provided. Cannot be used unless Verdict Mode is enabled.
Threshold minimum is 3. Time window must be between 5 and 60 seconds.
,verdict set <action> <threshold> <seconds>
Permissions: Server Owner or Antinuke Admin
View the current configuration of all Verdict Mode protections including enabled state, active protection count, and general settings.
,verdict config
Aliases: verdict status, verdict settings
Permissions: Server Owner or Antinuke Admin

Protection Modules

Verdict Mode monitors the following event types. Each can be toggled independently and configured with its own threshold and time window.

Anti Mass Ban

Triggers when a user bans multiple members within the time window

Anti Mass Kick

Triggers when a user kicks multiple members within the time window

Anti Channel

Covers channel deletions, creations, and permission overwrites — each tracked separately

Anti Role

Covers role deletions, creations, and permission changes — each tracked separately

Anti Webhook

Triggers when a user creates multiple webhooks within the time window

Anti Bot Add

Triggers when a user adds multiple bots within the time window

Anti Server Update

Triggers when a user makes repeated changes to server settings within the time window

Threshold Configuration

Each protection has two configurable values:
SettingDescriptionMinimumMaximumDefault
ThresholdNumber of actions required to trigger punishment33
WindowTime window in seconds actions are tracked within5s60s10s
For servers with active moderation teams that prune members frequently, consider raising the ban/kick window to 30s or more to avoid false positives from legitimate bulk actions.

Valid Actions for verdict set

InputProtection Targeted
banAnti Mass Ban
kickAnti Mass Kick
channelAnti Channel Delete
channelcreateAnti Channel Create
channelupdateAnti Channel Update
roleAnti Role Delete
rolecreateAnti Role Create
roleupdateAnti Role Update
webhookAnti Webhook Create
botAnti Bot Add
serverAnti Server Update

Control Panel Interface

Running ,verdict opens an interactive control panel built with Discord Components V2. The interface includes:
  • Real-time status display showing all protections grouped by category, their enabled state, and configured thresholds
  • Individual toggle buttons for each protection type
  • Global controls:
    • Enable All
    • Disable All
Only the user who ran the command can interact with the control panel. The panel becomes inactive after 2 minutes but remains visible.

Punishment

Verdict Mode always punishes with a permanent ban. There is no configurable punishment — the philosophy of Verdict Mode is that if someone has crossed the threshold, the only appropriate response is removal.

Exemptions

The following are always exempt from Verdict Mode regardless of threshold:
  • Server Owner — Always exempt, cannot be punished
Everyone else — including antinuke admins, whitelisted users, and whitelisted roles — is subject to Verdict Mode if they cross the threshold.

Difference from Standard Antinuke

FeatureAntinukeVerdict Mode
Whitelist bypassYesNo
Threshold-basedNoYes
Configurable punishmentYesAlways ban
Per-action time windowNoYes
Server owner exemptYesYes
Antinuke admin exemptYesNo

Logging Integration

Every Verdict Mode punishment is automatically recorded in the Antinuke punishment log, including the action that triggered it, the actor, the target, and the punishment applied.
All Verdict Mode actions are logged to your configured logging channel if enabled.

Best Practices

  • Enable Verdict Mode after your standard Antinuke is configured — they work best together as layered protection.
  • Start with default thresholds (3 actions in 10s) and adjust based on your server’s normal moderation activity.
  • If your staff regularly performs bulk actions (mass pruning, bulk role assignments), raise the relevant thresholds to avoid false positives.
  • Regularly review your config with ,verdict config.
Since Verdict Mode ignores whitelists, make sure your staff understand that crossing the threshold will get them banned regardless of their trusted status.