Palworld Breeding Combos: Check the Special Pair Before Averaging Scores
Rayhound + Foxcicle produces Rayhound Cryst; Tanzee + Flambelle produces Tanzee Ignis; Beakon + Frostplume produces Beakon Cryst. These are listed special combinations, not examples of choosing the child nearest the parents' average breeding power. Check an exact pair's special rule before applying ordinary score matching.
Checked 22 October 2026. Pair listings were cross-checked in Palpedia and PalDB. Score inputs and the ordinary midpoint formula come from OP.GG's current table. The calculations below are this site's arithmetic audit, not in-game tests or a claim that every historical version behaves identically.
Three candidate pairs to check in your save
| Parents | Listed child | Planning check |
|---|---|---|
| Rayhound + Foxcicle | Rayhound Cryst | Keep the Cryst suffix in the target; Rayhound alone is a different entry. |
| Tanzee + Flambelle | Tanzee Ignis | Do not substitute another Fire Pal merely because the target is Ignis. |
| Beakon + Frostplume | Beakon Cryst | Use the listed species, not an assumed interchangeability between Ice parents. |
Use opposite-sex parents for the farm setup. A listed species result does not promise desired passive skills, talents or a mutation. Keep those goals separate. For building, Cake-chest checks and egg collection, use the Breeding Farm plan.
Worked audit: the same shortcut fails in different ways
For ordinary score matching, define M = floor((A + B + 1) / 2). A and B are parent breeding powers. Define our audit difference D = C − M, where C is the listed special child's power. D is a bookkeeping comparison, not a game stat, probability, timer or strength rating. The source table supplies A, B and C; this page calculates M and D.
| Case | Source inputs A, B → C | Computed midpoint M | Computed difference D |
|---|---|---|---|
| Rayhound / Foxcicle → Rayhound Cryst | 1920, 1970 → 1600 | floor(3891 / 2) = 1945 | 1600 − 1945 = −345 |
| Tanzee / Flambelle → Tanzee Ignis | 2900, 2700 → 2830 | floor(5601 / 2) = 2800 | 2830 − 2800 = +30 |
| Beakon / Frostplume → Beakon Cryst | 1690, 860 → 580 | floor(2551 / 2) = 1275 | 580 − 1275 = −695 |
Rayhound case. The listed child's 1600 is below both 1920 and 1970. Relative to the lower parent, the separation is 1920 − 1600 = 320. Relative to the ordinary midpoint, it is 345. Neither separation is an efficiency gain: they demonstrate that the listed special child is not explained by simply averaging these parents. Do not “repair” the pair by finding another parent whose average is nearer 1600.
Tanzee case. The special child's 2830 lies inside the parents' 2700–2900 range, yet it differs from the computed midpoint by 30. This is the counterexample to an “outside the parent range means special; inside means ordinary” screening rule. That screen would flag the Rayhound case but miss this one. Check the exact pair listing even when a result looks numerically ordinary.
Beakon case. The midpoint is 1275, but the listed child's score is 580. Its distance below the lower parent's 860 is 860 − 580 = 280, different from the 695 midpoint gap. Record which comparison you mean. Calling both numbers a “breeding gap” without a definition makes a saved note ambiguous and can send a later parent search toward the wrong number.
What these cases establish. A large negative D and a small positive D both occur among these checked special pairs. Therefore neither closeness to the midpoint nor the sign of D identifies the rule branch. This conclusion is derived from the displayed rows; it is not an estimate of how frequently special combinations occur. D cannot discover an unlisted combination, either. It audits a candidate already backed by a pair listing.
A rule check before a long breeding project
Ordinary matching also needs the eligible child pool and tie handling; an average alone is not a complete calculator. Do not apply it to a pair with an explicit override. If references disagree, preserve both dated results and leave the candidate unverified rather than blending their numbers.
Download the printable combo score audit card. It contains the source inputs, formulas and a blank observation area. Save or print it as a reference, then use a fresh card for another check. It is not a calculator or a promise of reopening saved form fields.
Before extending a chain, distinguish the listed child from the child you actually hatched. Record the game build, exact parent names, source-check date and observed result. An unexpected result is a reason to re-check the pair and rule branch, not evidence that the displayed arithmetic changed. For general breeding and the existing project planner, return to the breeding guide.