Data operations
Editorial Policy
The map, skill tree and build library use explicit release labels and confidence states so incomplete data is not presented as settled fact.
Publication states
Structured records move through Draft, In review, Published, Needs review and Archived. The current static release contains published records and visibly labeled community leads. Expanded map coverage means reviewed records are combined with a pinned open-data snapshot; it does not imply complete container, nature or machine-spawn coverage.
Verification labels
Confirmed means the record is published, reviewed for the current data release and marked with confirmed confidence. Probable means the observation is useful but still requires current-release confirmation. Unverified is a lead and is excluded by the map's Only verified filter.
Skills and builds
Skill names, descriptions, rank caps, unlock thresholds and prerequisites are stored as versioned structured data. Editorial builds must identify their scenario, point split, strengths, tradeoffs, full allocation, picking order, author, reviewer and applicable release. We do not label one build universally best.
Patch workflow
When a game update may affect maps or skills, related records should be moved to Needs review until checked. Each public release receives an immutable release ID, visible game-data label and dated change record. Static deployment artifacts can be rolled back by redeploying the preceding validated build.
Corrections
Reports should identify the page, map or skill, explain the suspected error and include a reproducible observation when possible. See the correction form.