Source priority
Official patch notes and support pages define current rules. The wiki can add item, Investigation, and map details after those details are checked against the active build. Community posts and videos are used for a concrete route, visual tell, or interface demonstration, never as an unsupported guarantee.
When sources conflict, the newer official statement that directly addresses the same mechanic wins. The public guide contains only the resulting current instruction; the disagreement is not turned into a second workflow for the reader.
Reading and citation rules
- We read the relevant sources in full before writing a guide.
- We check the original official or Wiki page rather than relying on a search excerpt.
- Do not reproduce full articles, posts, or transcripts.
- Guides explain the action, its requirements, and the expected result.
- Use zero to three explanatory figures per guide. Every figure needs a source, a useful caption, and a specific detail the reader should inspect.
What each source must prove
A source link is not decoration. Its note states the exact rule, value, location detail, or visual observation it supports. If a source cannot support a useful current statement, it does not appear on the page.
Images retain their proportions and colors. Process diagrams are labeled and cite the rules they explain. Image provenance and compatibility checks are recorded separately; an older image is never relabeled as newly captured.
Official sources can establish rules. Wiki pages can supply structured detail. Community and video sources can demonstrate practice. None of them is allowed to create false precision beyond what was actually observed.