A wiki you can trust is one that publishes what it got wrong and fixed. Here is every correction we've made, plus how we tier each claim by how strongly it's backed.
Anonymous comments are never presented as equal to on-screen proof. When a mechanic isn't confirmed, we say so rather than guessing.
What changed: The homepage previously claimed we had “mapped every track to the helix loadout that wins it” and advertised a $1k→$100k economy path.
Why: Our Racing guide explicitly lists allele-to-track mappings as unverified, and the Money guide had already dropped the speculative economy path. The homepage now matches the verified guides.
What changed: The CRISPR Mapper tool now carries an EXPERIMENTAL badge and a disclaimer.
Why: Its phenotype outputs are an illustrative model, not verified game mechanics. The real allele-to-trait mapping has not been confirmed from save-file data, so it must not be read as in-game truth.
What changed: The site title changed from “The Definitive Horsey Game Wiki” to “The Verified Horsey Game Wiki.”
Why: We won’t call ourselves definitive until claims are save-file-backed with named testers. “Verified” describes what we actually do: cite a source for every number.
What changed: Build pages no longer promise real “DNA recipes” or “key helices.”
Why: The DNA strings on build pages are illustrative concepts, not values extracted from the game’s actual genome export format. We say so plainly until verified genomes replace them.
What changed: Early content described DNA as ten or twenty 0–9 sliders.
Why: The game actually stores DNA as 20 helices × 2 alleles, each a variable-length GCAT base-pair string (40 lines in the export). The old slider model was wrong and was deleted.
What changed: Where the game’s exact mechanics aren’t confirmed (weather effects, which helix governs which trait), we say “unverified” instead of asserting a number.
Why: Honest unknowns beat confident guesses. A claim we can’t back with on-screen proof is marked, not stated as fact.
Spotted something we got wrong? Email /contact with a source — we'll verify it and log the correction here.