Editorial Policy — Testing and Corrections

1. Three rules that decide everything

Test before publishing. A route, a timing window or a damage value is only stated as fact when we have seen it in the current build or when the source is strong enough to say so plainly.
Do not invent numbers. If a value is not confirmed, the page says it is unconfirmed. A blank is more useful than a plausible guess that sends someone into a boss fight with the wrong plan.
Show the disagreement. When sources conflict, the page presents both positions and says which one we used and why, instead of silently picking one.

2. How sources are ranked

Tier	What counts	How it is used
Primary	Our own capture on the current retail build	Stated as fact, with the build and date
Strong secondary	Established guide sites and wikis that show their own testing	Stated as fact when two independent sources agree; attributed
Weak secondary	Single posts, aggregators, unattributed lists	Mentioned only as a conflicting claim, never as the basis of a number
Unverified	Anything we could not check	Marked TODO with what needs testing

Every guide ends with a sources section listing what was used and when it was accessed. Sources are linked, not copied: we summarise the finding and link to the original rather than reproducing its text.

3. Conflicts get a table, not a coin flip

Boss names, health values, drop sources and ending conditions are the usual places where guides disagree. When that happens, the page gets a visible conflict section naming each claim, who makes it and what we do in practice. A reader who has seen a different number elsewhere should be able to find that number on our page and understand why we chose otherwise.

4. What a TODO means

A TODO marker is a promise that the gap is known. It appears when a value exists in the game but no reliable source has published it, or when two sources disagree enough that a test is needed. It is never used for something we simply forgot. When a TODO is resolved, the marker is removed, the date changes, and the correction is noted if the earlier text was wrong.

5. AI use

AI tools are used for drafting, restructuring and proofreading. They are not a source. Every factual claim — a boss name, a location, a damage number, an ending condition — is checked against a cited source or our own testing before it goes live, and anything that cannot be checked is marked TODO rather than generated. Pages are reviewed by a human editor before publication.

6. Screenshots and images

We use our own captures wherever possible. Each screenshot is credited with the platform it was taken on, the build or version, and how it was captured. We do not host official key art, character portraits, soundtracks or cutscene rips. The full rule, including how to request removal, is on the copyright page.

7. Dates and updates

Every guide shows a published date and an updated date. A page is re-checked when the game receives a patch that touches combat, progression or endings, and when a reader sends a credible correction. The updated date changes only when the content changes, not when a page is merely viewed or reformatted.

8. Corrections

Send the page URL, what is wrong, and — if you can — a screenshot or clip. We re-test, then either correct the page or explain why the existing text stands. Substantive corrections are noted at the bottom of the page. Email [email protected] or use the contact page.

9. Independence from advertisers

Advertising and affiliate revenue do not influence rankings, verdicts or which guides get written. Sponsored material would be labelled as sponsored and kept out of editorial guides. The affiliate disclosure explains the commercial side in detail.

Written in plain English on purpose. Last updated Nov 7, 2026. Questions go to [email protected].