How Palworld 1.0 Breeding Results Are Determined
A source-aware explanation of Palworld 1.0 special combos, CombiRank reconstruction, gender-dependent results, and breed-true Pals.
Last updated: 2026-08-06
What is a game fact and what is reconstructed here?
The local PAK exposes the Pal parameters and the special-combination table used in this audit. The calculator then reconstructs ordinary parent-to-child results from the extracted CombiRank values and checks the resulting graph against known outcomes. That makes the result useful, but it is important to say exactly what it is: the formula below is a data-backed reconstruction of the site's breeding engine, not a pretend quotation from an official public formula document.
The local verification baseline is Steam Build 24467282, PAK SHA-256 a82fee669e60558db5adc409c8607bb6c06b8a4d4c984317f9a37415461e7119, last verified 2026-08-05.
The result order used by the calculator
For a pair of species, the calculator applies the following order:
- A same-species pair returns that same species.
- A matching cross-species row in the extracted special-combination table wins first. The site has 136 cross-species special combinations in scope, and all 136 map to the local
DT_PalCombiUniquerows. - Otherwise, the engine calculates the rounded midpoint of the two parents' CombiRank values, then selects the eligible child whose CombiRank is closest to that midpoint. If two candidates are equally close, the higher CombiRank wins.
- The reverse lookup walks the same result graph, so a target page lists the parent pairs that the calculator can actually produce.
This is why a pre-1.0 chart can be wrong even when the species names look familiar: Palworld 1.0 revised the breeding order, and a changed rank can move an ordinary formula result. Check a pair in the current breeding calculator before spending Cake.
Special cases the page must not hide
Gender-dependent rows
Katress + Wixen has two game-defined outcomes because the source rows carry different parent-gender conditions. A species-only lookup must therefore show both possible children. The calculator keeps both rows instead of letting a map overwrite one with the other.
Breed-true results
The current breeding graph identifies 26 Pal entries with no parent pair from two other species. Most are Legendaries or former tower-boss fusion entries. “Breed true” means the target can be produced by pairing two of the same species; it does not mean that the species is forbidden from acting as a parent for other children.
For audit precision, 24 of those same-species rows are literal matches in the compared site scope; Panthalus and Astralym are handled by the calculator's explicit same-species fallback because the mapped special table does not contain their corresponding self rows. The result is shown as a graph rule, not mislabeled as 26 literal PAK rows.
Mutation is a separate evidence track
The compared DT_PalMonsterParameter table has no field corresponding to the site's old mutation boolean. This page and the calculator therefore do not present that boolean as a PAK-verified fact. The official Palworld 1.0 announcement discusses Mutation as a launch feature, but a launch note is not evidence for every individual Pal flag.
How to use the result in game
Open a target's breeding guide, inspect all available parent pairs, and use the path planner if you already have a Palbox to work from. Then assign one male and one female to a Breeding Farm, place Cake in the farm chest, and hatch the resulting egg. The calculator answers the species result; it does not promise a passive, active skill, talent, or Mutation outcome.
For a Pal's capture route, open its detail page. It combines the current map snapshot with the same breeding graph, and it explicitly says when no wild or Alpha point is present instead of inventing a location.
Evidence boundary
This page covers the fields and relationships actually checked in the local audit: species identity, parameters, work records, map capture rules, special combinations, the reconstructed formula, and the reverse parent graph. It does not claim a complete drop database, passive inheritance probability, active-skill table, player save state, or universal work-speed multiplier. Those need their own evidence before they belong in an accuracy-sensitive page.