Player Genome Case Study — What the DNA Tool Confirms (and Can't)

Player Genome Case Study — What the DNA Tool Confirms (and Can't)

🔬 What this is. An original, reproducible check we ran ourselves. We took the three community-submitted genomes on our Player Genomes page (all shared by u/JimboIsDaMan), fed each one through this site's DNA Database engine, and recorded the exact output. The genome strings and the in-game names/phenotypes are the submitter's; the parsing, round-trip, hash, and structure numbers below are ours and you can reproduce every one of them by loading each genome with the links provided.

Most "genome" content online just reposts a DNA string and a screenshot. This page does the opposite: it takes strings people actually shared and asks a narrow, checkable question — does our tool read them losslessly, and what can we honestly say about their structure?

Method

For each genome we ran five deterministic steps in the DNA Database engine:

1. Parse the raw text export into a 20-helix × 2-allele structure.
2. Re-serialize it back to text and confirm it is byte-identical (text round-trip).
3. Hash-encode it to the shareable URL form, then decode the hash back and confirm the genome is unchanged (hash round-trip).
4. Count homozygous (locked) helices and the G/C/A/T base composition.
5. Compare it against all 18 catalogued species presets to find the true nearest — and whether "nearest" is even meaningful.

Everything below is the literal output of that run.

Results

All three carry the full 20 helices, each allele is a valid GCAT string of the fixed per-helix length, and every one survives both the text round-trip and the hash round-trip with zero drift. That is the concrete, reproducible thing the tool proves: it reads and re-emits real player exports without corrupting them.

What the "nearest species" number actually means

This is where a lot of genome write-ups quietly overreach. Our tool can report a "nearest catalogued species," but for heavily edited genomes that label is close to meaningless:

• MR Backflip and The Big Flipper differ from the nearest preset in all 20 helices — and that 20/20 distance is tied across all 18 presets. There is no single "nearest" species; they are fully bespoke. Listing one preset name would be an artifact of tie-breaking, not a finding.
• Moonwalking Human is the interesting one: it is homozygous at all 20 helices (fully locked, no heterozygous sites) and sits 19/20 from both Horse and Man simultaneously. So the honest statement is "roughly equidistant from Horse and Man," not "a Horse."

We updated the Player Genomes page to say exactly this rather than name a single species.

What this does not prove

To be clear about the limits — the tool verifies format and structure, not gameplay:

• We have not verified that any of these produce the claimed in-game creature (a horse that backflips, a race champion, a moonwalking human). Those are the submitter's community-tier claims, labelled as such on /genomes.
• We have not confirmed which helix drives which trait — the helix→trait mapping is still unverified (see How DNA Actually Works).
• Base composition and homozygosity are real measurements, but they are not a speed or performance rating.

Load them yourself

Each genome on /genomes has a one-click Load in DNA Database button; open it, then export and diff it against the string shown on that page to repeat the round-trip:

• MR Backflip on /genomes
• The Big Flipper on /genomes
• Moonwalking Human on /genomes

If you have a timed, on-video run of any of these genomes in-game, send it via /contact — that is the piece we can't produce ourselves, and it would upgrade these from "format-verified" to "gameplay-verified."

Last updated: 2026-09-08. The structural figures on this page were produced by running each genome through this site's DNA engine and are reproducible from the strings on /genomes. In-game phenotypes are community-submitted and unverified.