Route sheet 03 / boundary reference
Rules reference.
No dated effective server rules revision is available. This page keeps that field Unknown, separates safety guidance from server policy, and names what a usable revision must contain.
- Rules revision
- Unknown
- Gap checked
- 2026-07-18
- Claim class
- Unmeasured / no source record
Required shape / future effective revision
Four things a usable boundary must answer.
- Gameplay scope
- What the premise permits in-world: building, raiding, player conflict, traps, and any stated exceptions.
- Service boundary
- Conduct outside ordinary play, including attacks on the service, credential theft, doxxing, and illegal content.
- Enforcement
- Who can act, what evidence is considered, and whether a decision has a published challenge route.
- Revision history
- An effective date and change record that make edits visible instead of silently replacing the boundary.
Current reading / narrow by design
What this page can safely say.
Safety guidance
Do not share credentials, recovery codes, session tokens, private personal information, or unknown client files. This is protective guidance, not a claim about an effective server rule.
Server-specific detail
Gameplay policy, resets, permitted clients, automation, restoration, monetization, enforcement, and appeals are Unknown as of 2026-07-18.
A dated effective revision belongs here and in the change record. Until one exists, the absence is the fact; use support routing only to carry a question, not to infer an answer.