Evidence protocol
Editorial and Corrections Policy
Every important claim carries an evidence level. The label tells you whether a detail came from the developer, a repeatable gameplay check, or an unconfirmed community report.
- Publisher
- How to Fish Field Guide Editors
- Last updated
Three evidence levels
Steam store data, developer announcements, official patch notes, and developer-authored statements. These establish platform, version, feature, and change-log facts.
A direct gameplay check that records the game build, input method, difficulty, location, prerequisite state, action, and observed result. Screenshots or video are included when they materially help verification.
A community finding that has not yet been reproduced. Reported information stays visibly qualified and cannot support a definitive title, answer, or working-status badge by itself.
Publishing gate
- The page answers its target question near the beginning.
- Game-specific names, controls, values, and outcomes are sourced or tested.
- The checked patch and verification date are visible.
- Known failure cases and evidence limits are stated.
- Sources link to the exact material used, not only a generic homepage.
- Only then is the page made indexable and added to the XML sitemap.
Updates and corrections
Patch-sensitive pages are checked after official updates that could change their answer. A page date changes only when its factual content or verification materially changes.
When sources disagree, the conflict is shown and the more specific, current evidence is preferred. Confirmed errors are corrected in place. You can send a correction with the page URL, game version, and supporting capture or source.
Independence and safety
The site does not sell rankings or accept undisclosed paid placements. Mods, trainers, executable downloads, and exploit claims require extra caution; a third-party tool is never described as a vanilla game feature.