karen
Back to Features
Co-Owner Engine

Extra Owner
System

Allows server owners to appoint highly trusted administrators with near-total control over security features, bridging the gap between staff and the primary owner.

1

High-Level Access

Extra Owners can toggle Anti-Nuke, configure punishments, and manage the whitelist — actions restricted from regular admins.

2

Security Hierarchy

Strictly enforced: Only the Primary Server Owner (User ID matches guild.ownerId) can manage the Extra Owner list.

3

Scalability & Limits

Supports up to 10 unique Extra Owner slots per server, allowing for a robust senior security team.

4

Zero-Latency Sync

Changes are instantly synchronized between MongoDB and the in-memory engine for real-time protection updates.

Technical Specifications

  • Database: Persisted via extraowner array in models/antinuke.js.
  • Cache Engine: Managed via extraOwners Set in antinukeMemory.js.
  • O(1) Lookups: Utilizes isExtraOwner() for millisecond permission checks.
EXTRA OWNER CONTROL
// Appoint a trusted security co-owner
›
!extraowneradd <user>or !eo add
// Revoke high-level co-owner status
›
!extraownerremove <user>
// Open interactive co-owner management panel
›
!extraownerpanel
// [Owner Only] Reset entire co-owner list
›
!extraownerresetOwner Only
Ownership Integrity

The primary server owner remains the ultimate authority. Extra Owners cannot remove the primary owner or each other — preventing hostile takeovers within the co-owner tier.