breeding tool
Breeding calculator
Covers every combination for 206 breedable Pals. Results are calculated from extracted CombiRank data and override tables, with rule type, derivation chain, data version and 1.0 status.
Status note
Pending 1.0 verification means the current version is calculable, but 1.0 still needs regression. It is neither invalid nor confirmed for 1.0.
After selecting parents, the result shows child, rule type, derivation chain and 1.0 status.
After selecting a target child, all usable parent combinations are listed from formula reverse lookup plus overrides.
Calculates one feasible path with the fewest breeding steps. Intermediate partners are assumed separately obtainable and no save data is read.
Calculation rules (reproducible)
| Rule type | Calculation | Source |
|---|---|---|
| formula | child = the Pal in the formula pool whose CombiRank is closest to floor((rankA + rankB + 1) / 2); exact ties use the verified winner table. | PalDB extraction layer (data/*.json) |
| special_override | 98 special override combinations are entered row by row and take priority over the formula. | PalDB extraction layer (data/*.json) |
| gender_locked | The Wixen / Katress line can return different children by parent gender direction and cannot be treated as an unordered pair. | wiki.gg / Host Havoc baseline; direction samples are recorded in the data contract. |
| self_only | 12 Pals can only be obtained by same-species pairing (legendaries and some exceptions). | PalDB extraction layer (data/*.json) |
| same_species | Same-species pairing always returns the same species. | PalDB extraction layer (data/*.json) |
Why manual calculations may differ
When manual calculations and tool results differ, the cause is usually one of these: the formula is only the base rule, ties have a separate winner table, special combinations override the formula, gender direction is not interchangeable, or the data version is different. The derivation chain labels which rule was hit.
| Common difference | How the tool handles it | Player next step |
|---|---|---|
| Only using the CombiRank average | The general formula is only the base rule; overrides, gender direction and self-only breeding can change the result first. | Read the rule type beside the result, not only the child name. |
| Tie handling is missing | When two candidates are equally close to the target value, the verified tie-winner table decides the child. | If your manual value lands between two Pals, check whether the derivation chain shows tie handling. |
| Special overrides were missed | 98 override combinations are entered row by row and take priority over the formula; manual formula checks are expected to fail on these. | If the result rule type is special_override, formula verification does not apply. |
| Treating parents as an unordered pair | gender_locked samples preserve parent direction and do not automatically treat A+B and B+A as the same case. | Read the gender-direction FAQ |
| Different data version | Site data was extracted on 2026-07-02, baseline current patch pre-1.0 (v0.7.3); the table you have may be older. | Read data sources |
| Mixing old tools or community sheets | Third-party tables, old wiki copy and player experience are research leads, not the site's data canon. | Read data sources |
| Treating current results as a 1.0 promise | Current data is calculable, but pre-1.0 rows stay marked "Pending 1.0 verification"; status is written back only after the T0-03 regression samples pass. | Read status guidance |
T0 regression samples (QA set)
The 27 rows below are the data-layer acceptance set: every data re-extraction must recalculate all of them before publish. They are also the first regression targets after 1.0. Current status: Pending 1.0 verification.
| Parent A | Parent B | Current child | Rule type | 1.0 status | Why it matters |
|---|---|---|---|---|---|
| Penking | Bushi | Anubis | formula | Pending 1.0 verification | formula regression coverage sample |
| Jormuntide | Suzaku | Suzaku Aqua | special_override | Pending 1.0 verification | special_override regression coverage sample |
| Vanwyrm | Anubis | Faleris | special_override | Pending 1.0 verification | special_override regression coverage sample |
| Relaxaurus | Grizzbolt | Orserk | special_override | Pending 1.0 verification | special_override regression coverage sample |
| Mossanda | Petallia | Lyleen | special_override | Pending 1.0 verification | special_override regression coverage sample |
| Mossanda | Rayhound | Grizzbolt | special_override | Pending 1.0 verification | special_override regression coverage sample |
| Kitsun | Astegon | Shadowbeak | special_override | Pending 1.0 verification | special_override regression coverage sample |
| Elphidran | Surfent | Elphidran Aqua | special_override | Pending 1.0 verification | special_override regression coverage sample |
| Helzephyr | Frostallion | Frostallion Noct | special_override | Pending 1.0 verification | special_override regression coverage sample |
| Jormuntide | Blazehowl | Jormuntide Ignis | special_override | Pending 1.0 verification | special_override regression coverage sample |
| Wixen Female | Katress Male | Wixen Noct | gender_locked | Pending 1.0 verification | gender_locked regression coverage sample |
| Wixen Male | Katress Female | Katress Ignis | gender_locked | Pending 1.0 verification | gender_locked regression coverage sample |
| Anubis | Frostallion | Bastigor | special_override | Pending 1.0 verification | special_override regression coverage sample |
| Neptilius | Jormuntide Ignis | Silvegis | special_override | Pending 1.0 verification | special_override regression coverage sample |
| Jormuntide Ignis | Silvegis | Knocklem | special_override | Pending 1.0 verification | special_override regression coverage sample |
| Menasting | Knocklem | Menasting Terra | special_override | Pending 1.0 verification | special_override regression coverage sample |
| Quivern | Lullu | Quivern Botan | special_override | Pending 1.0 verification | special_override regression coverage sample |
| Gobfin Ignis | Finsider | Finsider Ignis | special_override | Pending 1.0 verification | special_override regression coverage sample |
| Sootseer | Ghangler | Ghangler Ignis | special_override | Pending 1.0 verification | special_override regression coverage sample |
| Chillet Ignis | Whalaska | Whalaska Ignis | special_override | Pending 1.0 verification | special_override regression coverage sample |
| Neptilius | Bastigor | Cryolinx | formula | Pending 1.0 verification | formula regression coverage sample |
| Neptilius | Bellanoir Libero | Suzaku | formula | Pending 1.0 verification | formula regression coverage sample |
| Bastigor | Foxparks Cryst | Rayhound | formula | Pending 1.0 verification | formula regression coverage sample |
| Silvegis | Foxparks Cryst | Foxcicle | formula | Pending 1.0 verification | formula regression coverage sample |
| Jetragon | Jetragon | Jetragon | self_only | Pending 1.0 verification | self_only regression coverage sample |
| Paladius | Paladius | Paladius | self_only | Pending 1.0 verification | self_only regression coverage sample |
| Necromus | Necromus | Necromus | self_only | Pending 1.0 verification | self_only regression coverage sample |
Should old high-investment lines be kept for 1.0? (retest priority)
The rule is three steps: keep first, mark as pending, regress in the first T0 batch. Official messaging confirms the 1.0 change surface is broad, but before the change list is public nobody can identify exactly which breeding chain fails. Do not dismantle high-investment individuals early, and do not treat them as guaranteed unchanged.
| Retest order | Target | Reason for this priority |
|---|---|---|
| First batch | special_override chains | Override rows are entered one by one; any official change directly changes the result, and historical answer drift concentrated here. |
| Second batch | gender_locked combinations | The sample count is small and the rule is special, so formula regression alone is unlikely to catch every change. |
| Third batch | pure formula chains | If CombiRank and the tie table do not change, formula chains remain valid as a group; sampled regression covers them. |
Data contract
| Field | Current value | Frontend meaning |
|---|---|---|
| source | paldb.cc (/json/iv_{en,tw,ja,cn}.json, /en/{PalName}, /en/api/pal_breed_2a, /en/api/pal_breed_3) | Extraction-layer endpoints; the site does not copy competitor tables or prose. |
| extracted_at / baseline | 2026-07-02 / current patch pre-1.0 (v0.7.3) | All results apply to this version baseline; status is written back from regression samples after 1.0. |
| QA | 27/27 | Regression samples must pass before the data layer is published. |
| contract | Ludbase wiki: breeding-tool-contract | The breeding tool must preserve rule type, evidence source and version status. |
Applicable versionP1 route contract / P2 v2.0 content layer
Updated
SourcePalDB extraction layer (data/*.json)
UpstreamConOps current focus: Palworld P2 content-layer rebuild