Multi-locus Compounds

Some named morphs are not a single trait. They are the visual combination of two genes that happen to look distinctive together — a phenotype the breeder community gave a name to, even though there's no single allele that makes them.

Examples in the catalog:

  • Sunglow (Boa Constrictor) = Albino (recessive) + Hypo (codominant)
  • Ghost (Boa Constrictor) = Hypo (codominant) + Anery (recessive)
  • Snow (Corn Snake) = Amelanistic (recessive) + Anerythristic (recessive)
  • Snow (Western Hognose) = Albino (recessive) + Axanthic (recessive)
  • Snow (Kenyan Sand Boa) = Albino (recessive) + Anerythristic (recessive)
  • RAPTOR (Leopard Gecko) = Tremper Albino (recessive) + Eclipse (recessive)
  • Bumble Bee, Killer Bee, Firefly, Spinner Blast, Stinger Bee (Ball Python) — designer combos of codominant/dominant genes (Killer Bee = Super Pastel + Spider)

Blizzard (Leopard Gecko) is not on this list: it's its own single recessive gene, distinct from Murphy Patternless (Blizzard × Murphy Patternless gives normal-looking double hets).

A Sunglow Boa is genetically a homozygous Albino plus at least one copy of Hypo. The "Sunglow" label describes the look, not a separate gene.

Why these can't be a single trait in the catalog

If you list Sunglow as a "single recessive trait" with the rest of the recessives, the calculator breaks predictably. A Sunglow × Sunglow cross would predict 100% Sunglow babies — but in reality, those babies follow Mendel on two separate loci:

  • Albino × Albino → 100% visual Albino ✓
  • Hypo × Hypo → 25% Super Hypo + 50% Hypo + 25% normal

A "Sunglow" baby is one that's both visual Albino and at least het Hypo. That's not a single number you can predict cleanly without modelling the underlying two genes.

How the catalog handles them

For each of these compounds, the catalog has a combo entry with inheritance marked unknown. The entry points at its components (Albino + Hypo for Sunglow):

  • The Sunglow entry has unknown inheritance, linked to Albino + Hypo as components.
  • When the calculator sees unknown, it returns the honest note: "outcomes vary — modelled as a multi-locus compound." No invented percentages.
  • When you breed and the calculator runs on the underlying Albino + Hypo traits (which the parents carry separately), it produces correct per-locus predictions.

This means: don't pick "Sunglow" as the trait on a Sunglow boa. Pick Albino visual + Hypo visual instead. The Sunglow combo entry exists for catalog browsing and historical-record purposes, but the calculator works correctly only when the parents carry the underlying components as separate traits.

That's a real ergonomic compromise. The plan to make multi-locus compound names work end-to-end (you pick "Sunglow" and the form automatically splits it into Albino + Hypo) is on the roadmap but not built today.

Single-locus vs multi-locus — the contrast

A common confusion. Compare with Allelic complexes:

| | Single-locus compound | Multi-locus compound | |---|---|---| | Mechanism | Two alleles at one gene | Two genes interacting | | Example | BEL (any two BluEL alleles) | Sunglow (Albino + Hypo) | | Calculator | Punnett via the locus engine — gives clean percentages | Marked unknown, returns "outcomes vary" | | Catalog entry | Two separate traits sharing a locus | One combo entry pointing at the components | | Saved as | Two traits on the animal | The combo entry |

A BEL is one animal with two BluEL traits (Mojave + Lesser, or whichever). A Sunglow is one animal with two traits from two different loci (Albino + Hypo). Both look like "two traits on the animal," but the mechanism is different — and it shows up the moment you breed them.

Designer combos of codominant genes

The ball python "bee" combos (Bumble Bee = Pastel + Spider, Killer Bee = Super Pastel + Spider, …) are combo entries with unknown inheritance too. If they were treated as a single codominant gene, Bumble Bee × Bumble Bee would predict a "Super Bumble Bee" and miss that 25% of those embryos are the non-viable Super Spider — and Bumble Bee × normal would read 50/50 instead of splitting four ways (Bumble Bee / Pastel / Spider / Normal).

Record the components instead (Pastel + Spider, or Pastel Super + Spider for a Killer Bee) and the calculator gets everything right, lethal filter included.

The same goes for animals that are a super form: a bearded dragon Silkback is Super Leatherback and a leopard gecko Super Giant is homozygous Giant — record them as Leatherback / Giant with expression Super.

Known gap: Salmon Glow

Salmon Glow is the Boa Constrictor compound of Salmon (a Hypo synonym) + Albino — same shape as Sunglow, just with the Salmon line of Hypo. It is not in the catalog today. Adding it would be the same shape as Sunglow: a combo entry pointing at Salmon + Albino with unknown inheritance.

Similar gaps may exist for Diablo Blanco (RAPTOR + Murphy Patternless? evidence shaky) and other named multi-locus combos. Until the calculator learns to surface multi-locus compound names end-to-end, adding more of these would just mean more entries that emit "outcomes vary." So the catalog ships only the four where the name is established and the underlying components are non-controversial.

For the per-species coverage of what is and isn't included, see Catalog and the species page (e.g. Boa Constrictor).

Try it

Double het Snow × Double het Snow shows the 1-in-16 Snow; the calculator puts the combo name back on matching babies.