A checked build for each guide
A build label describes that guide’s checked rules, not a site-wide promise. Source-review dates and dated statistics serve different purposes: a Steam count is an observation at the printed time, not a live value. Updating one guide does not certify unrelated articles for a newer patch.
Each topic has one public article. When its rules are checked against a later build, that article is updated and its own version label changes.
Verification order
- Read the newest official patch in full and list every affected workflow.
- Use current official rules before wiki or community explanations.
- Verify dynamic values, access conditions, and cycle rewards in the current client where possible.
- Use community sources for observable practice, not guaranteed rates or spawns.
- We review affected guides, images, and sources before updating the version shown on the site.
When a guide is allowed to update
A page updates when a reliable source changes a rule that affects a player action. System workflows come first, followed by item access, raid modes, monsters, maps, medicine, and technical data. A text-only fix does not trigger unrelated rewrites.
A community report can start verification, but it cannot establish a new rule by itself. Until the change is confirmed, the affected guide retains its last checked build and date. A source review does not imply a hands-on test.