FINALRULES v1.0CMAI-S0-R1.0
Season Zero
tournament rules.
The complete operating contract for an authorized Minecraft red-team event: one supplied client, one private arena, one fixed detector stack, and evidence that every scored run can be replayed.
01
Entry, format & consent
Season Zero is a solo-or-duo event. Every entrant and every tester must be named on the application, accept RULES v1.0, and actively consent before receiving the qualifier pack.
- Entrants may withdraw before a scored run without penalty.
- All participants are told what telemetry is recorded and how the simulated staff checks work.
- Scored-run logs, server replays, and submitted artifacts are retained for 30 days after the final, then deleted unless an entrant asks for earlier deletion.
No unsuspecting player, moderator, server owner, or tester may be involved. A team that adds an undisclosed tester is disqualified.
02
Organizer-controlled tournament stack
The competition runs only on infrastructure operated by the organizer. The network address is withheld from the public and issued to accepted entrants in the signed qualifier pack on 11 January 2027.
- Game
- Minecraft: Java Edition 26.2
- Client loader
- Fabric Loader 0.19.3 on Java 25
- Server
- Paper 26.2, private allowlist, fixed challenge seed
- Anti-cheat
- GrimAC 2.3.73
- Scoring plugin
- CMAI JudgeBridge 1.0.0
- Protocol
- CMAI-Arena/1 signed challenge-response handshake
The qualifier pack includes the exact server configuration, detector configuration, dependency locks, challenge-map hash, and artifact checksums used for scoring.
03
Activation & technical containment
The experimental entry must remain dormant until the tournament client receives a valid, time-limited CMAI-Arena/1 handshake from the organizer-controlled server. The handshake binds the server identity, event build, entrant ID, and session expiry.
- Invalid, missing, expired, replayed, or mismatched handshakes must leave every experimental feature disabled.
- Disconnecting, changing server, or losing validation must disable those features immediately.
- The mod must fail closed on single-player, LAN, Realms, public servers, and every non-event address.
- Judges must be able to verify the gate from source and from a negative test build.
04
Permitted features
Within an authenticated event session, teams may build and score the following:
- Navigation, planning, aim assistance, automated input, recovery, and objective-solving agents.
- Client-side movement or combat assistance designed for the supplied challenges.
- Packet timing and shaping against the event server's test instrumentation.
- Resource-pack presentation changes used as part of the submitted system.
- Event-only synthetic telemetry spoofing intended to test GrimAC and JudgeBridge detection.
- Defensive detector modules entered in the Detector Lab track.
“Spoofing” here means synthetic event telemetry inside the closed arena—not account, identity, device, network-origin, or authentication spoofing.
05
Forbidden behavior
Any item below causes rejection or immediate disqualification, regardless of score:
- Testing or activating the entry on a public, third-party, LAN, Realms, or non-event server.
- Obfuscation, packing, encrypted payloads, hidden modules, self-modifying code, or withholding source.
- Persistence, autostart, privilege escalation, process injection, security-tool interference, or any other OS modification.
- Reading, requesting, storing, transmitting, or imitating passwords, tokens, cookies, session data, launcher data, or other credentials.
- Microsoft/Mojang session spoofing, authentication bypass, IP or proxy-origin spoofing, HWID/device spoofing, or OS fingerprint spoofing.
- Scanning, exploiting, damaging, or accessing infrastructure outside the supplied event interface.
- Undisclosed remote control, post-freeze downloads, external command-and-control, harassment, or involving anyone who did not consent.
06
Detector & simulated admins
GrimAC 2.3.73 is the scored anti-cheat. CMAI JudgeBridge 1.0.0 is the event plugin that timestamps and deduplicates its alerts, records objective completion, and produces the signed run ledger.
ADMIN SIMULATION TEAM
Organizer-controlled spectator bots and scripted staff-check scenarios act as “fake admins” inside the arena. They observe, teleport, message, and request predetermined actions to test whether an entry remains consistent under scrutiny. Every entrant knows these are simulations; they never impersonate real staff outside the event.
Experimental/verbose detector output is visible in raw logs but does not score. Repeated alerts from the same Grim check inside a five-second window are one deduplicated alert. A staff-confirmed impossible-state event requires the run ledger and replay to agree.
07
Fixed scoring model
Each accepted entry receives one seeding run and two scored runs. The higher valid scored run counts. All teams use the same map hash, challenge seed, configuration, and time limit.
| Category | Points | Method |
|---|---|---|
| Detector evasion | 30 | Starts at 30. JudgeBridge subtracts 1 point per deduplicated GrimAC alert and 5 per staff-confirmed impossible-state event, to a floor of 0. |
| Arena performance | 25 | Five deterministic objectives worth 5 points each. Partial completion is awarded only at published checkpoints. |
| Simulated-admin evasion | 15 | Three disclosed staff-check scenarios worth 5 points each: protocol compliance (2), behavioral consistency (2), and clean recovery (1). |
| Containment & reliability | 15 | Valid handshake and fail-closed behavior (8), no unauthorized network or filesystem access (3), and a crash-free scored run (4). |
| Review & reproducibility | 15 | Clean rebuild from submitted source (6), source-to-log traceability (5), and replay reproduction of the scored result (4). |
| Total | 100 | Ties: containment, then detector evasion, then arena performance. |
A disqualification overrides the numerical result. Judges publish the signed ledger and category totals for every finalist.
08
Source, builds, logs & replay
The source freeze is an auditable submission, not just a mod file. Judges must be able to produce the same artifact and replay the same evidence.
- Complete unobfuscated source for the mod, resource pack, models, scripts, and native components.
- Build instructions, pinned toolchain, dependency lockfiles, license inventory, and SHA-256 hashes.
- A clean-room build whose resulting artifact hash matches the submitted release, or a documented deterministic-difference report.
- Client log, server log, JudgeBridge ledger, Grim alert export, map hash, event configuration, and synchronized replay for each scored run.
- A capability manifest mapping every feature to its source files, runtime permission, and log events.
Judges may reject dependencies that disappear, cannot be licensed for review, or perform undeclared network or filesystem operations.
09
Season Zero dates
Rules v1.0 published
Applications and consent
Qualifier pack and private arena access
Source and artifact freeze
Closed scored arena
Final showcase and award
All cutoffs use UTC. A schedule change requires a numbered rules amendment published to every accepted entrant; silent changes are not valid.
10
The big reward surprise—revealed
GUARANTEED WINNER REWARD
Season Zero Champion Cape
The highest-scoring valid entry receives one unique animated cape rendered in the supplied tournament client, a permanent Season Zero winner badge on the event site, and first entry to the next CMAI arena.
Honest disclosure: this is an event cosmetic, not an official Mojang or Minecraft cape. It has no promised cash value, no blockchain component, and no guaranteed visibility outside the CMAI tournament client. No cash prize is offered.