Editorial principles
- Start from a real player question. A page should help the reader take a next step.
- Separate source types. Official information, database data, community reports and editorial inference are not interchangeable.
- Prefer current evidence. Patch-sensitive statements should show a version or check date.
- Make the result executable. Use steps, conditions, tables, screenshots, timestamps and failure checks.
- Show limitations. Uncertainty and missing first-hand testing remain visible.
Source hierarchy
Sources are labeled by what they can reliably support. A source can be useful without proving every conclusion drawn from it.
1. Official sources
Patch notes, developer announcements and official documentation are preferred for changes, intended mechanics and policy.
2. Current databases and wikis
Used for properties, identifiers and structured facts, with current-version checks.
3. Independent guides and videos
Used to compare practical approaches and reproduce user-facing workflows, not to copy complete pages.
4. Community discussions
Used to identify real questions, confusing UI states and possible bugs. A single comment is not treated as proof of a universal rule.
First-hand testing and verification
Source-verified content is not described as personally tested. A page may be published when its claims are sufficiently supported, but it must not use phrases such as “we tested” or “our gameplay showed” unless first-hand evidence exists.
When first-party testing is unavailable, the page should say so and make the source, version and uncertainty visible.
Third-party material
- YouTube videos should use official embeds.
- Reddit posts and comments should use official embeds or short, attributed quotations.
- Other guide sites may be used for research and comparison, not copied as complete pages.
- Original diagrams, licensed assets and first-party screenshots are preferred.
Corrections and rights requests
Corrections should identify the exact page, the disputed statement and a supporting source. High-impact factual errors are prioritized, but response times are not guaranteed. Rights and attribution requests can be sent through the Contact page.