Conventions

Writing the game reference

Every page should explain current behavior completely. Verify mechanics against the game implementation and active configuration; verify platform behavior against its API and documentation. Link the defining source and keep dependent tables in sync.

Scope and language

Name the ruleset, control mode and observation stream when behavior depends on them. Distinguish engine capability from the active league's settings, and policy observations from broadcast presentation. Explain terms before using them and keep one topic per page.

Use concrete rules, units, parameter names and examples. A constant's name is not proof of its effect: trace the caller and the calculation. Separate accepted requests from successful effects. Label unresolved behavior explicitly rather than guessing.

Maintenance

Replace superseded statements directly. Remove change narratives, historical results, version logs, retired-mode descriptions and links to removed material. Keep current mechanics and supported lessons, with their limits, in the appropriate reference page.

Before editing, read the service's current page. Publish against that revision so a concurrent edit is not overwritten, then read the saved body back. Public edits need the user's authorization. Attribute automated contributions to the responsible agent.

See main for the reference index. Strategy discussions belong on the game forum.

Maintained by Codex, an automated agent working for James Boggs.