Calvert Cliffs: MRL - Raider Guidelines

onyxllc · August 6, 2026, 12:55am

RAIDER RULES & GUIDELINES

Note: Do not attempt to reason with Security. Doing so results in disciplinary action for both parties.

There are different “classes” of raiders:
- Class A: Base tier weaponry, includes the P90 and Glock 19.
- Class B: Referred to as the “Heavy Weapons” gamepass. Includes the Desert Eagle and AUG.
Class Matching
- Please attempt to match classes. This applies to Security: try to use the same class of weaponry to engage a fair fight. Security are not required to play the game, so this goes both ways.

Section 01: Area Control Restrictions

Constraints upon Raiders regarding facility hardware and containment zones within the PNIFR-04 Reactor Complex.

Control Room Lockdown Restriction: Raiders are strictly prohibited from initiating a lockdown of the Reactor Control Room under any circumstances. Triggering a lockdown in this zone unfairly disrupts core facility infrastructure.
EEDS Command: Raiders are fully authorized to seize, occupy, and lock down the EEDS Room to suppress manual employee intervention.

Section 02: EEDS Room Sabotage

System Failure Trigger: During the Bunker Buster Event, defensive systems initiate automatically but encounter a rapid system failure. Lockdown doors open to allow operations personnel to conduct repairs.
Tactical Objective: Raiders must establish absolute control of the EEDS Room, secure the perimeter, and neutralize any personnel attempting to restore system integrity or disarm the incoming threat.

Section 03: Rules of Engagement

Engagement permissions are determined by target alignment, behavior, and tactical threat assessment:

Security Team Personnel
- Status: Instant Kill on Sight (KoS)
- Warnings: None required
Cooling Reactor During Forced Meltdown
- Status: Countermeasurer
- Warnings: 3 Valid Warnings required (unless actively engaged in countermeasure operations)
Attempting to Repair EEDS / Stop Incoming Threat
- Status: Countermeasurer
- Warnings: 1 Valid Warnings required
Leaking Raider Positions to Security
- Status: Hostile Combatant (Risk to Self)
- Warnings: Kill on sight allowed for a single life
Standard Employees & Maintenance
- Status: Non-Combatant (Protected)
- Warnings: Mandatory 3 Valid Warnings required prior to engagement

Section 04: Warning Escalation Protocols

Non-security targets require strict adherence to the following escalation sequence before lethal force is authorized:

First Warning: Clearly communicate demands via chat or voice communications (e.g., halt movement, vacate console).
Second Warning: Explicitly repeat the directive, allowing a reasonable timeframe for compliance.
Third & Final Warning: Issue the final order. Authorize engagement if non-compliant or if hostile actions continue.

Active attempts to cool or stabilize the core during a forced meltdown.
Interacting with EEDS controls to execute repairs or halt incoming annihilation events.
Active membership and deployment on the Security team.
Transmitting Raider coordinates, positions, or movements via communications channels.

Section 05: Anti-Abuse Policy & Game Bans

The Raider team drives conflict, core sabotage, and dynamic gameplay elements.

Minor Abuse (Failing to issue proper warnings to non-security personnel): Official Warning
Moderate Abuse (Unauthorized Control Room lockdowns, spawn camping/killing, repeated RDM): Temporary Ban (7 Days)
Critical Abuse (Exploiting, cross-team griefing, persistent administrative defiance): Permanent Ban

If you would like to report a user on the Security or Raider team, please contact us in our communications server.