Duplicates collapse
If both parents carry the same passive, the current community model treats it as one candidate. A duplicate is not double weight.
Palworld 1.0 · evidence-bounded breeding guide
Five-second answer
Offspring can inherit passives carried by either parent. In the current reverse-engineered community model, duplicate copies of the same passive collapse to one candidate, so duplicates do not add extra weight.
A pinned July 27, 2026 PalCalc extraction from a sampled Steam build exposes a 4:3:2:1 parent-inheritance count array. PalCalc's community model maps it to 40/30/20/10 for attempting 1/2/3/4 inherited passives. It does not prove the exact chance that a finished egg has your desired clean set.
For four desired passives, minimize unwanted unique passives, hatch and keep cleaner partial wins, then backcross while keeping the target species route valid.
Keep the species result valid
Passive inheritance and child-species selection are separate problems. Check the pair before scaling a hatch batch.
Current community reverse engineering describes a single pool formed by taking the union of both parents' passive skills and removing duplicates. The inheritance selection is then made from that unique pool. Pocketpair has not published this full algorithm as an official probability specification, so the page labels it accordingly.
If both parents carry the same passive, the current community model treats it as one candidate. A duplicate is not double weight.
A junk passive that appears on only one parent is still a unique candidate. Cleaner donors reduce the number of inherited choices competing with your desired set.
In this model, a clean 2+2, 3+1, or 4+0 split is mainly a way to arrive at the same target unique pool. It is not an official Pocketpair recommendation for a preferred parent split.
Community sources agree that offspring can receive passives not selected from the parent pool, but current public descriptions disagree on how the second/random-add roll should be interpreted.
PalCalc's pinned July 27, 2026 extraction reads a sampled Steam build's passive-inheritance weight array as 4:3:2:1. Its community model maps those weights to attempts to inherit one through four passives from the parent pool. That is useful evidence for thecount roll in that sample, not an official formula for the current game or the final egg.
| Attempted inherited passives | Community-model weight | Safe interpretation |
|---|---|---|
| 1 | 40% | Weight for the parent-inheritance count roll, not the finished egg's exact target-set success chance. |
| 2 | 30% | Weight for the parent-inheritance count roll, not the finished egg's exact target-set success chance. |
| 3 | 20% | Weight for the parent-inheritance count roll, not the finished egg's exact target-set success chance. |
| 4 | 10% | Weight for the parent-inheritance count roll, not the finished egg's exact target-set success chance. |
The pinned sampled-build settings also expose a second passive-related weight array. The current Palworld Wiki describes a conditional second roll, but its clean-pool probability table is not coherent with that description on the same page. PalCalc's solver uses a separate independent random-add interpretation and documents the underlying reverse engineering as not fully verified. Those community interpretations do not justify one shared exact target-success table.
PalGenetics therefore does not render the unresolved second-step values as an independent public probability distribution and does not publish an exact chance for completing a specific clean set.
The pinned sampled-build count weights and the community deduplicated-pool model support practical advice to keep the parent pool small and clean.
Do not read 40/30/20/10 as four independent slot chances or as a guarantee that a specific desired passive is selected.
The count roll, the actual unique pool, random extras, special sources, and the four-slot cap all matter before a final outcome can be modeled.
Practical method
Use a selection workflow instead of pretending each egg has one exact, published success rate. The goal is to improve both the passive pool and the child-species route generation by generation.
Write the final set before you breed. A clear target makes it obvious which offspring are progress and which are only temporary donors.
Under the current community model, the parents contribute one combined list of unique passives. Keep unwanted unique passives out of that list whenever possible.
A 2+2 split is easy to reason about, but the community model cares about the resulting deduplicated pool rather than which parent owns each passive. A clean 3+1 or 4+0 arrangement can serve the same purpose.
Make sure the selected parents still produce the target species. Passive planning and species-result planning are separate constraints.
Keep offspring that move the line toward a cleaner target pool. Two or three desired passives on a cleaner child can be more useful than an older donor with extra junk.
Pair the best partial child with the donor that restores missing targets while adding the fewest unwanted unique passives. Repeat instead of assuming one hatch has a published exact success rate.
A child with all desired passives plus an unwanted extra is not the final clean build. It can still be a useful intermediate only when it improves the next parent pool.
Prefer the offspring that preserves more of your desired set while reducing unwanted unique passives in the next pairing. A partial hatch can be a better breeder even when it is not the final Pal.
Check a parent pair →Version-sensitive boundaries
Current breeding documentation treats Lucky and Legend as inheritable when a parent already carries them. Keep the boundary clear: inheritable from a parent does not mean available as an ordinary random extra.
Pocketpair says Special Cake increases the chance of inheriting multiple passive skills from Pal parents. The official notes give the direction of the effect, not an exact modified percentage.
Pocketpair describes Mutation as a low-chance breeding result that can produce a stronger Pal with a unique passive skill. This page does not infer an exact mutation rate or a universal inheritance rule for every mutation-only passive.
Pocketpair's Palworld 1.0 notes establish implants as an official way to change passive skills. Community documentation supports only a limited set of implant-compatible passives, so do not assume every passive is injectable or use Surgery availability as evidence for breeding probability.
Version note: the English Steam public notes checked on 2026-08-13, through v1.0.3 dated August 11, 2026, do not announce a replacement passive inheritance formula. That absence is not proof that every internal detail is unchanged; special-passive eligibility and item availability should still be rechecked after game updates.
Secondary examples
These are compact target-set examples after you understand the inheritance workflow. They are not a complete passive database and do not claim one four-passive set is best for every Pal, patch, or job.
| Role | Example target set | Boundary |
|---|---|---|
| Combat | Legend · Demon God · Serenity · flex slot | Example target set. Use the fourth slot for the element, survivability, or utility your Pal actually needs. |
| Worker | Remarkable Craftsmanship · Artisan · Work Slave · Insomnia | Work-speed example. SAN, food use, ranching, and work suitability can justify a different fourth slot. |
| Mount | Legend · Swift · Runner · Infinite Stamina | Travel-focused example. A combat or stamina trade-off can be better for a specific mount. |
| Breeding farm | Philanthropist · role-specific support passives | Breeding-farm example, not a universal four-passive prescription for ordinary base workers. |
Evidence & version notes
Supports Palworld 1.0 terminology, Mutation as a low-chance stronger breeding result with a unique passive, and Special Cake as increasing inheritance of multiple parent passives. It does not publish exact passive inheritance percentages.
Read official 1.0 changelog ↗A July 27, 2026 PalCalc change scrapes the breeding inheritance arrays from a sampled Steam build instead of relying on typed constants. This supports the 4:3:2:1 count weights in that sample, but not their presence in every current build or every downstream interpretation of the second roll.
Inspect pinned datamine change ↗Supports the deduplicated parent-pool description, Lucky/Legend parent inheritance, and a conditional X/Y description. Its clean-pool probability table is not coherent with that description on the same page, so PalGenetics does not use the table as confirmation.
Read community breeding documentation ↗Sources checked August 13, 2026. Community reverse engineering is labeled as such. Agreement between community sites is not treated as independent confirmation. PalGenetics is an independent fan site and is not affiliated with or endorsed by Pocketpair.
Direct answers
Current reverse-engineered community documentation combines both parents' passives into one deduplicated pool, then selects passives from that pool. Duplicate copies of the same passive do not add extra weight. The exact treatment of the later random-extra step is not coherent across current public sources, so PalGenetics does not publish an exact finished-set probability from it.
A pinned July 27, 2026 PalCalc extraction from a sampled Steam build exposes a 4:3:2:1 weight array for the parent-inheritance count. PalCalc's community model maps it to 40%, 30%, 20%, and 10% for attempting to inherit 1, 2, 3, or 4 parent passives. Those sampled-build weights are not an official Pocketpair probability table and are not exact odds of finishing a specific clean target set.
PalGenetics does not publish an exact clean-pool success percentage for the current game. The pinned July 2026 PalCalc extraction reproduces count weights for its sampled Steam build, but community and Wiki descriptions disagree on how the second/random-add roll is applied. Until that interpretation is version-scoped and independently reproducible, an exact target-success percentage would overstate the evidence.
Not under the current deduplicated-pool community model. The same passive on both parents contributes one unique candidate, so duplicating it is not treated as double weight.
Define the four-passive target, build the cleanest combined parent pool you can, confirm the species route, hatch and keep cleaner partial wins, then backcross those offspring until the final child has the desired set without unwanted extras. Use the calculator to keep the species result valid while you improve the passive line.
Current community breeding documentation treats Lucky and Legend as eligible for inheritance when a parent already carries them. That does not mean they are ordinary random-extra passives, and PalGenetics labels this as community evidence rather than an official Pocketpair probability statement.
Pocketpair's Palworld 1.0 release notes say Special Cake increases the chance of inheriting multiple passive skills from the parents. Pocketpair does not publish an exact modified percentage there, so PalGenetics does not invent one.
Pocketpair describes Mutation as a low-chance breeding result with higher stats and a unique passive skill. Its Palworld 1.0 notes establish Surgery Table implants as an official feature, while community documentation supports only a limited set of implant-compatible passives. Treat both as separate acquisition or correction tools, not proof of the inheritance odds on this page.
The generated PalGenetics mechanic data used by this page caps the passive set at 4. The page does not use that local data to infer an exact success rate for any target set.
Related tools & actions
Confirm the child from two parents or reverse-find parents.
Choose a target species and open its parent options.
Separate species-result rules from passive inheritance.
Start from useful pairings, then clean the passive pool.
Review the species-outcome ranking model and its limits.
Open a concrete target page and compare parent routes.