How our guides are verified

The process

• Multiple independent sources. No guide is built from a single video. Where several complete guides exist for a map, the steps are cross-checked line by line against all of them.
• Cross-checked against gameplay. Steps are checked against recorded play, not just against other write-ups — which is how second-hand errors get caught.
• Solo and co-op documented separately wherever the behaviour differs.
• Original and remastered versions separated where a map exists in more than one form.
• Randomised steps identified as randomised. If a puzzle changes per match, the guide says so and teaches the rule — and where the rule is algorithmic, ships a solver for it.
• Community corrections reviewed. Disputes are carried openly until they resolve rather than being quietly decided.
• Unconfirmed information is labelled and never presented as fact.

What the labels mean

• Confirmed — corroborated across multiple independent sources, or verified first-hand.
• Community-reported, confirmation pending — reported by a credible source but not yet independently corroborated. Usable, but treat as provisional.
• Disputed — sources actively disagree. Both readings are published, with what separates them.
• Documented gap — the step exists but nobody has published a reproducible method. Named as a gap rather than filled with a guess.

When we get something wrong

Corrections are published in the guide itself, not buried. Where a previously published method turns out to be wrong, the page states the correct method and why the old one appeared to work — because an explanation that produces the right outcome for the wrong reason will otherwise keep coming back.