karen
Back to Features
Isolation Engine

The Quarantine
System

A non-destructive alternative to outright banning. When a user triggers Anti-Nuke thresholds, the system strips their power and places them in temporary isolation — preserving their data for review.

1

Role Generation & Hardening

Automatically creates a secure Quarantine role with zero permissions (0n bitfield) across the entire server if it doesn't already exist.

2

Snapshotting the Threat

Takes an intelligent snapshot of roles (oldRoles) and dangerous permissions before stripping them, backed up directly to MongoDB.

3

Power Stripping & Fail-Safe

Instantly revokes all roles and assigns Quarantine. Defaults to a Ban if role assignment fails due to link role or API limits.

4

Evasion Prevention

Detects if a malicious user leaves and re-joins, immediately re-quarantining them before they can act.

Summary for Server Owners

  • No Data Loss: Preserves chat history & server profile versus Kick/Ban.
  • Easy Recovery: Restore previous roles instantly from the MongoDB snapshot.
  • Fail-Safe: Seamlessly falls over to a Ban if role hierarchy prevents quarantine.
QUARANTINE
// Open interactive quarantined registry
!quarantinelist
// Instantly restore user roles
!quarantinerelease <user>
// Mass release everyone in registry
!quarantineresetallCaution
// Preemptively quarantine suspicious account
!quarantineadd<user> [reason]
Security Infrastructure

Quarantine actions are strictly locked behind the isAuthorized guard. Only the Server Owner or registered Extra-Owners can manage the registry — rogue staff cannot bypass or revert their own isolation.