Allowed sources
| Source | Use case |
|---|---|
| Official website | Primary launch, campaign, and navigation source. |
| Official social posts | Short-form announcements and campaign updates. |
| Official store pages | Platform, region, install, and availability details. |
| In-game notices | Reward, event, and live-service corrections. |
| In-game testing | Routes, drop checks, reset timing, banner rules, and combat behavior after launch. |
| Beta data | Temporary context only when clearly labeled and likely to change. |
Verification order
- Check the official website or in-game notice first.
- Confirm the same fact on another official source if possible.
- Write cautious copy if only partial details are visible.
- Move older assumptions into version history when facts change.
Rumor handling
| Input | How to handle it |
|---|---|
| Rumor or leak | Do not publish as confirmed guide data. |
| Unclear official teaser | Use cautious wording and avoid final gameplay claims. |
| Beta-only value | Label as beta and move changes into version history after launch. |
| Conflicting sources | Prefer the latest official or in-game source and log the correction. |
Update rules
- Do not promote leaks or rumors to confirmed status.
- Separate tested launch data from pre-launch placeholders.
- Keep source references visible on major hub pages.
- Update the source policy when official site behavior changes.
Source policy FAQ
Should fan sites be used as primary sources?
No. Fan sites can help with discovery, but they should not replace official verification.
Where are corrections tracked?
Use the corrections page and page updates for visible maintenance notes.