Methodology: How We Verify Every Guide
How we source facts, score confidence, handle conflicting sources, and re-verify guides within 48 hours of every game patch.
Why guides go wrong
Most game guides are written once, in the launch window, and never touched again. When the developer patches difficulty, damage numbers, or parry timings, those guides silently become wrong — and nothing on the page tells you so.
That is the problem this site exists to solve. We treat a guide as a view over a database of individually sourced facts, not as a document. When a patch invalidates a fact, we can find every page that depends on it.
Where facts come from
Nothing enters our database without a source URL, a retrieval date, and the game version it was checked against. Source type sets a baseline confidence score:
| Source type | Base confidence |
|---|---|
| Official patch notes | 0.95 |
| Official website / dev blog | 0.92 |
| Official wiki or in-game data export | 0.90 |
| Our own in-game testing (recorded) | 0.90 |
| Community wiki with edit history | 0.75 |
| Reddit answer with 50+ upvotes | 0.60 |
| Video guide captions | 0.55 |
| Scattered forum discussion | 0.40 |
Confidence rises when independent domains agree: two domains add +0.05, three or more add +0.10, capped at 0.98. Nothing is ever certain enough to score 1.00. A claim below 0.60 confidence cannot carry a guide's core conclusion on its own — it needs corroboration.
When sources disagree
We do not merge conflicting claims, and we do not let a model pick the more plausible one. Contradictions are recorded as disputed, both versions are kept, and the guide says so in plain language instead of stating a number we cannot stand behind.
Every guide shows its disputed-fact count in the Fact Integrity panel near the bottom of the page.
What happens when a patch lands
- Detect. We monitor official patch notes and log each release with the entities it touches.
- Invalidate. Every fact attached to an affected entity is marked for re-check, and every guide referencing those entities is flagged.
- Re-verify. A human re-runs the affected content in-game against the new build.
- Publish. Guides get an updated version stamp, and the patch tracker records what changed and how many guides were revised.
Our target is 48 hours from patch to re-verified guide. Until a guide has been re-checked, it carries a visible warning stating the build it was written for — we would rather show you a stale label than a confident wrong answer.
How AI is used here
We use AI to draft prose from facts that are already in the database, and to help extract structured data from source material. It is not permitted to invent numbers: generation is constrained to facts that carry a source, and output is checked against the database before publishing.
Judgement calls — which sources to trust, how to resolve a dispute, whether a tactic actually works after a patch — are made by a person. We tell you this because a site that hides it is usually hiding something worse.
Corrections
If a guide is wrong, we want to know. Every page lists its sources so you can check our work. Corrections are applied to the underlying fact, which means they propagate to every guide that depends on it, not just the page you were reading.