Antinuke Administrators

Designate trusted users to manage antinuke protections without server ownership

Overview

The Antinuke system uses a three-tier permission hierarchy to give server owners fine-grained control over who can manage security settings. Extra Owners act as co-owners for antinuke purposes, while Antinuke Admins have limited access to enable protections only.

Antinuke Admins can enable protections but cannot disable them or change punishments. For full access, use the Extra Owner system instead.

---

Access Control

Action	Server Owner	Extra Owner	Antinuke Admin
Manage extra owners	✅	❌	❌
Manage antinuke admins	✅	✅	❌
Enable protections	✅	✅	✅
Disable protections	✅	✅	❌
Change punishments	✅	✅	❌
Configure Verdict Mode	✅	✅	❌
Exempt from punishments	✅	✅	✅
Can be removed	❌ Never	✅	✅

---

Extra Owners

Extra Owners have elevated antinuke access equivalent to the server owner. They can manage antinuke admins, enable and disable protections, change punishments, and configure Verdict Mode.

Extra Owners have near-full antinuke control. Only assign this role to highly trusted users.

Commands

extraowner add

Add a user as an extra owner to grant them elevated antinuke access.

Syntax

~extraowner <@user>

Aliases: eo, xowner
Permissions: Server Owner only
Limit: 3 extra owners per server

extraowner remove

Remove a user from the extra owner list.

Syntax

~extraowner remove <@user>

Aliases: eo remove, xowner remove
Permissions: Server Owner only

extraowner list

View all extra owners for your server.

Syntax

~extraowner list

Aliases: eo list, xowner list
Permissions: Server Owner only

---

Antinuke Admins

Antinuke Admins are trusted users who can enable antinuke protections. They cannot disable protections, change punishments, or access Verdict Mode configuration.

If you need a user to have full antinuke control, use Extra Owner instead of Antinuke Admin.

Commands

antinukeadmin add

Add a user as an antinuke administrator.

Syntax

~antinukeadmin <@user>

Aliases: ana, antiadmin
Permissions: Server Owner or Extra Owner
Limit: 3 admins per server

Antinuke admins can only enable protections. If you want them to also disable or configure punishments, add them as an Extra Owner instead.

antinukeadmin remove

Remove a user from the antinuke administrator list.

Syntax

~antinukeadmin remove <@user>

Aliases: ana remove, antiadmin remove
Permissions: Server Owner or Extra Owner

antinukeadmin list

View all antinuke administrators for your server.

Syntax

~antinukeadmin list
~antinukeadmin

Aliases: ana list, antiadmin list
Permissions: Server Owner or Extra Owner

---

Privilege Summary

Extra Owner

Extra owners can:

• Enable and disable all antinuke protections
• Change punishment types for any protection
• Manage antinuke admins (add and remove)
• Configure and toggle Verdict Mode
• Set and modify the log channel
• Access and use all antinuke commands

Extra owners cannot:

• Add or remove other extra owners
• Override the server owner

Antinuke Admin

Antinuke admins can:

• Enable antinuke protections
• View protection status and configuration
• Access antinuke commands that don’t require full access

Antinuke admins cannot:

• Disable protections
• Change punishments
• Manage other antinuke admins or extra owners
• Configure Verdict Mode

Limitations

Neither extra owners nor antinuke admins can:

• Manage extra owners (server owner only)
• Override the server owner’s decisions
• Modify server ownership
• Bypass antinuke protections themselves

---

Slot Limits

Maximum Limits

• Extra Owners: 3 per server
• Antinuke Admins: 3 per server

The server owner and bot developers do not count toward either limit.

---

How It Works

1. Server Owner Level

   The server owner has supreme authority over the entire antinuke system. They are the only one who can manage extra owners and cannot be removed from antinuke access.

2. Extra Owner Level

   Extra owners have near-full antinuke access. They can manage antinuke admins and configure all protection settings except managing extra owners themselves.

3. Antinuke Admin Level

   Antinuke admins have restricted access. They can enable protections to help respond to threats, but cannot alter the overall configuration or disable existing protections.

4. Regular User Level

   Standard members cannot access any antinuke commands and are subject to all active protections. They can be whitelisted separately to exempt them from punishments.

---

Best Practices

1. Use Extra Owners for Trusted Co-Admins

   Assign extra owners to users who need full antinuke control, such as co-owners or head admins.

   ~extraowner @TrustedCoOwner
   

   Extra owners can disable protections and change punishments. Only assign this to users you fully trust.

2. Use Antinuke Admins for Limited Staff Access

   Assign antinuke admins to moderators who should be able to activate protections during an attack but shouldn’t be able to alter the configuration.

   ~antinukeadmin @SecurityModerator
   
3. Keep Numbers Minimal

   Use as few slots as necessary. Extra owners especially should be kept to 1-2 users maximum.

   ~extraowner list
   ~antinukeadmin list
   
4. Regular Audits

   Review both lists periodically, especially after staff changes.

   ~extraowner list
   ~antinukeadmin list
   
5. Remove Access Immediately When Needed

   Promptly remove users who are no longer trusted or active.

   ~extraowner remove @FormerStaff
   ~antinukeadmin remove @InactiveUser
   

---

Troubleshooting

Cannot add — maximum reached

Problem: You’ve hit the 3-user limit for extra owners or antinuke admins.

Solution:

1. View current list: ~extraowner list or ~antinukeadmin list
2. Remove an inactive user: ~extraowner remove @user or ~antinukeadmin remove @user
3. Add the new user

User already added

Problem: Trying to add someone who’s already in the list.

Solution: Check the current list with ~extraowner list or ~antinukeadmin list.

Cannot add the server owner

Problem: Attempting to add the server owner.

Explanation: The server owner automatically has full access and doesn’t need to be added to either list.

Cannot add bots

Problem: Trying to add a bot as an extra owner or antinuke admin.

Explanation: Only human users can be added. Bots should be managed through the whitelist system instead.

Permission denied on antinukeadmin command

Problem: Cannot manage antinuke admins.

Explanation: Only the server owner and extra owners can manage antinuke admins. Regular antinuke admins cannot add or remove other admins.

Permission denied on extraowner command

Problem: Cannot manage extra owners.

Explanation: Only the server owner can manage extra owners. Extra owners themselves cannot add or remove other extra owners.

Antinuke admin cannot disable protection

Problem: Antinuke admin tries to disable a protection and gets denied.

Explanation: This is by design. Antinuke admins can only enable protections. To disable protections, the user needs to be an extra owner or server owner.

---

Security Recommendations

Trust Verification

Thoroughly vet users before granting extra owner access. They can disable your entire antinuke configuration.

Minimal Access

Use antinuke admin instead of extra owner whenever full access isn’t strictly necessary.

Regular Reviews

Audit both lists monthly or after any staff changes to ensure only active, trusted members have access.

Immediate Revocation

Remove access immediately if you notice suspicious behavior or if an account is compromised.

---

Related Features

Antinuke System

Explore all antinuke protection modules and the main control panel

Whitelist System

Exempt users from antinuke punishments without giving them configuration access

Verdict Mode

Threshold-based antinuke system accessible to server owners and extra owners

Antinuke Logs

Configure a dedicated channel to monitor all antinuke events