Section 1: Rights and Responsibilities
Definitions of roles and individual obligations under investigation.
Subject Classifications:
- The Suspect: The player flagged or formally accused of system rule violations.
- The Requester: The player submitting a formal report or initiating an inspection demand.
🛡️ Rights of the Suspect
- Permitted to locally capture video of their device entirely during the inspection for verification; staff cannot terminate recordings.
- May NOT refuse the execution of
Echo,Ocean, ordetect.actools. - Holds the right to request an alternate ScreenSharer. If no alternate staff arrives within 7 minutes, the inspection must proceed with the assigned examiner, or be flagged as refusal.
- Retains the right to appeal punishments and request an escalation to an active SS Manager.
⚖️ Duties of the Requester
- Must produce a clear, unedited capture of the initial "don't log" command sent within game logs.
- The "don't log" directive must be explicitly visible to the Suspect via Global Chat (Team Chat commands are invalid).
- Requests are only valid when submitted directly from an active game session.
- Prohibited from system misuse. Submitting inspection calls to break player win-streaks or prevent participation is subject to severe penalties.
Section 2: Protocols and System Limitations
Operational limits, systemic timeouts, and physical device handling regulations.
Timing Frameworks
Submission Limit: Must request the inspection within 7 minutes of the initial game where the "don't log" message was logged.
Session Window: An inspection session is capped at 1 hour and 30 minutes maximum (special event guidelines override this).
Ticket Lifespan: If an inspection ticket remains unclaimed by a staff member for 10 minutes, it is automatically deemed expired.
Frequency and Safe-Logs
Request Cap: Players are limited to two active requests against the same suspect daily. The absolute community-wide limit is five total inspections per individual, per day.
Unclaimed Requests: Expired or unclaimed tickets do not count towards active daily limits.
Premature Logs: If a suspect disconnects before staff is formally assigned, they cannot be banned for refusal. Execution requires an initiated session.
Device Compliance & Modification Policies
- Possession of cheat modifications on local hardware is permitted; however, they cannot have been run in the active PC session. If software was initiated, a full hardware reboot is required prior to joining PRBW.
- Disabling macros through software panels is insufficient. Hardware profiles must be entirely deleted from local mouse software directories.
Section 3: Classification of Violations
Detailed forensic boundaries distinguishing Severe, Medium, and Light offenses.
Severe Offenses
1. Illicit Client Modifications (Cheating):
Detection of active, unallowed mechanical advantages, including but not limited to:
auto-clickers, aim assist, reach modifiers, movement manipulation hacks, NoHitDelay, HitDelayFix, or
Render cheats/ESPs, executed within the current boot cycle. No anti-forensic attempts
detected.
⚠️ Action Note: Voluntary admission of cheating prior to tool execution guarantees a significantly reduced ban duration.
2. Active File Manipulation: Manually deleting, clearing, or modifying directories post "don't log" warning. This includes purging the Windows Recycle Bin, executing Shift + Delete, or editing mouse profile configs immediately before inspection.
3. Active Anti-Forensics (Bypass Attempts):
Clearing USN Journal logs,
restarting diagnostic system services, wiping system registry values, running
memory/disk cleaners, altering Prefetch files, emptying Shell:recent caches, or shifting system
clocks.
Using Alternate Data Streams (ADS), physically disconnecting storage devices, executing task scheduling cheats, FAT32 directory swapping, registry edits, NodeJS/Visual Studio scripting, execution of Process Hacker, System Informer, ProcMon, or PowerShell script bypasses.
Pre-scheduled Command Prompt commands, scripting routines, deleting system tasks, or launching PC optimization suites immediately prior to active inspection.
Switching operating systems/hardware systems mid-procedure, utilizing public anti-forensics suites, or displaying multiple combined layers of defense evasions. Note: This includes possession of custom bypass clients (e.g. Scoped, Dopium, or Cold Client) during the season.
Medium Offenses
1. Stalling Tactics: Delaying inspection compliance or ignoring ticket alerts. Lack of activity within the ticket is not excused. Suspects have exactly 7 minutes to join. If active presence is established, this is extended to 15 minutes for technical preparation. Queueing for active matches will result in immediate non-compliance.
2. Active Inspection Refusal: Declining to transmit AnyDesk connection codes, trolling behavior during active links, or controlling mice/keyboards manually during examination.
3. Termination of Tooling: Closing active Minecraft clients, client directories, or terminating the AnyDesk connection before the staff member has issued formal completion.
4. Disabling System Services: Intentionally
disabling core system components: SysMain, DPS (Diagnostic
Policy), Task Scheduler,
EventLog, BAM, DusmSvc, PcaSvc, or CDPSvc_*.
Optimization software is not accepted as an excuse. This also includes:
— Terminating BAM inheritance
patterns.
— Registry manipulation of Prefetch or
PcaSvc.
— Purging JumpLists or disabling PowerShell
logging threads.
Light Offenses
1. Forensic Inability: Absence of administrator privileges, severe networking or PC failure rendering connection impossible, or accidental client crashes.
2. Missing Mouse Configurations: Lack of proper mouse configuration software when software support exists for your device hardware model.
3. Multiple Mouse Hardware: Operating the device with more than one active mouse connected to USB ports during a system boot cycle.
Section 4: Sanction Progression Table
Standardized punishments applied to offenses on subsequent detections.
Section 5: Internal Staff Regulations
Codes of conduct governing ScreenSharers during active sessions.
Local Recording Protection: Staff are strictly prohibited from terminating, disrupting, or demanding the closure of any live local device recording configured by the Suspect.
Malicious Intent and Safety: Staff are strictly prohibited from deploying unauthorized tooling, keyloggers, remote access trojans (RATs), or implementing destructive configuration changes to the Suspect's PC environment.
Compulsory Session Recording: Staff must record the active screen execution of the entire ScreenShare session. If the recording software suffers a technical crash, recording must be re-established within 1 minute of the crash occurrence.