Required user permissions
modules.antinuke.bypass.request.createmodules.antinuke.bypass.request.read
Creating and reading use separate nodes. Review and revocation may additionally require explicit Anti-Nuke reviewer authorization from server configuration.
Subcommands /anti-nuke is a group command. Choose one of the interactions below.
/anti-nuke request Request a temporary bypass for yourself.
/anti-nuke request <minutes> <reason>
Arguments Duration from 1 minute to 7 days.
Why the bypass is needed, up to 256 characters.
Example Request a 30-minute maintenance bypass.
/anti-nuke request minutes:30 reason:"Role migration"/anti-nuke mine Show your current request or active bypass.
/anti-nuke mine
Arguments This interaction takes no arguments.
Example /anti-nuke cancel Cancel your pending request.
/anti-nuke cancel
Arguments This interaction takes no arguments.
Example /anti-nuke list List your requests or an authorized review queue.
/anti-nuke list [status] [limit]
Arguments Queue to display.
Default: Mine
Choices: MinePendingActiveReviewed
Maximum items, up to 100.
Example List pending requests.
/anti-nuke list status:Pending limit:25/anti-nuke review Approve or reject a pending request.
/anti-nuke review <user> <decision>
Arguments Whether to approve or reject.
Choices: ApproveReject
Example Approve a request.
/anti-nuke review user:@Moderator decision:Approve/anti-nuke active List active temporary and permanent bypasses.
/anti-nuke active [limit]
Arguments Maximum temporary entries, up to 100.
Example List active bypasses.
/anti-nuke active limit:25/anti-nuke revoke Revoke your bypass or, when authorized, another user's.
/anti-nuke revoke [user]
Arguments Another user; omitted to revoke your own bypass.
Example