Editorial policy

Evidence and scope

We use direct developer explanations and attributed player reports. A player report can support a useful action in that player’s demo context; we do not silently turn it into a universal control mapping. Each guide identifies its source and checked date.

Unknowns and changes

When sources disagree or the exact step is missing, we state the uncertainty and narrow the instruction. We recheck demo steps against released-build evidence or material patches before extending them to a new build.

Corrections

We use attributed developer statements, published walkthroughs and player reports. We do not describe source review as our own gameplay testing. A report from one version or one player does not establish a universal rule.

English guides are the source for translations. To report a correction, identify the page, language and exact statement involved. Review dates describe the content checked; they do not mean that every later patch has been tested.

We correct a page when a current developer source, a clear player demonstration or reproducible gameplay contradicts it. Material changes receive an updated checked date and explanation.