Roleplay Limitations & Server Violations
Prohibited Roleplay Scenarios: High-consequence structural plots, localized asset/protocol exploits, unverified faction structures, rogue operations, coordination setups outside baseline frameworks, or unauthorized tactical roles.
Penalties and Disconnects: When disconnected or removed via server execution, you are required to wait a minimum of 30 minutes before returning to active play. Wilderness camping scenes must stay localized within mountainous environments or recognized HRP sectors. Urban displacement scenarios must occur exclusively within back alleys or structured subterranean parking modules.
Rule 1: Fail Roleplay (FRP)
Failing to comply with active event scenarios. This includes ignoring vehicle damage states, declining structured containment procedures, or failing to acknowledge local environment updates. Proper scenario adherence is mandatory.
Rule 2: No Intention to Roleplay (NITRP)
Engaging in systemic disruption, low-effort interactions, or lingering in unresponsive states (AFK) for extended periods without actively contributing to the server ecosystem.
Rule 3: Non-Realistic Driving
Operating machinery at velocities exceeding 120+ units or exhibiting erratic, unpredictable navigation behavior that directly matches standard arcade mechanics over simulation.
Rule 4: Vehicle Damage Match (VDM)
Discharging armaments tracking directly onto transportation units without continuous narrative justification, or weaponizing rolling assets to eliminate pedestals without disengaging the target frame.
Rule 5: Random Lethal Engagement (RDM)
Initiating critical aggressive conflicts or tracking downstream damage loops against players without prior conversational framework or verified engagement parameters.
Rule 6: Framework Asset Abuse (TA)
Spamming interaction controls, rendering duplicate deployment entities, or deploying map objects to destabilize platform vectors or physical vehicle engines.
Rule 7: Conduct Infractions
Disruptive targeted behavior directed toward community operators or administrative units. This is assessed objectively based on systemic disruption metrics.
Rule 8: Unrealistic Customization (UA)
Deploying avatar models that conflict with standard scaling metrics, custom geometries, or frame heights provided within regular core platform parameters.
Rule 9: Scene Interruption
Intentionally intersecting or entering ongoing moderation perimeters or active administrative actions. Continued violations will result in progressive account adjustments.
Rule 10: New Life Rule (NLR)
Upon character standard operational failure, all memories, immediate spatial configurations, and active grudges connected to that specific interaction layer must be wiped.
Rule 11: Restricted Restraints
Deploying binding devices, tactical locks, or physical restraints without clear, audible, or textual programmatic confirmations via standard communication codes.
Rule 12: Automated Processing
Bypassing manual booking phases, custody steps, or core departmental administrative tasks by immediately executing terminal interface updates.
Rule 13: Voice Channel Disruptions
Transmitting high-amplitude sound loops, musical broadcasts, or disruptive audio signals through proximity tracking mechanisms is strictly restricted.
Rule 14: PA System Violations
Abusing local departmental amplifiers or specialized vehicle address components to broadcast audio distortion, overlapping frequencies, or unvetted media.
Rule 15: Latency Management
During severe bandwidth drops or tracking updates, operators must minimize velocity or move assets clear of central thoroughfares until baseline connection registers clean.
Rule 16: Proxy Moderation
Bypassing the standard report portal to dictate rules directly to other operators. All perceived structural breaches must be channeled directly to the moderation unit.
Rule 17: Damaged Asset Operation
Navigating transit options while the underlying component emits critical emission plumes or active smoke markers during active operations or pursuits is forbidden.
Rule 18: Compliance Exceptions
Refusing direct procedural directives issued by active administration personnel. Explicitly refusing containment tracking loops from public units will result in immediate network disconnects.