Palworld 1.0 Passive Skill Inheritance Planner

Use the Palworld 1.0 passive skill inheritance planner without invented odds

The Palworld 1.0 passive skill inheritance planner is designed for the decision you can verify before an egg is produced: whether the passive skills you want are present on at least one selected parent. Choose up to four target skills, mark the skills carried by Parent A and Parent B, and review the coverage summary. A target marked Covered is available in one or both parent pools. A target marked Missing is not present on either parent, so that pair cannot pass it directly from the traits you entered. This is a coverage check, not a promise about the next egg.

Version 1.0 added new passives, World Tree passives, and mutation-only passives while also adding cakes that influence breeding outcomes. The official release notes describe those effects qualitatively but do not publish a complete numeric inheritance formula. For that reason, this planner does not display a success percentage, an expected egg count, or a guaranteed combination. It keeps the useful planning step and leaves unsupported numbers out. If a future verified formula becomes available, probability can be added behind the same versioned data gate without changing what today’s coverage result means.

Build the target list before choosing a parent pair

Start by choosing the final role of the Pal. A combat mount, a base worker, a ranch Pal, and a breeding carrier usually need different passive sets. Select only the skills that matter to that role and keep the target list at four or fewer. A shorter, deliberate list is easier to audit than a large wish list containing mutually unhelpful effects. Read each skill description rather than relying on rank alone. Some high-rank skills include a tradeoff, while a lower-rank skill may solve the exact movement, work, defense, or elemental problem in your build.

Next, enter the passive pool on each candidate parent exactly as it appears in game. Do not add a skill merely because that species can sometimes have it; the planner needs the traits on the individual Pal you intend to breed. When a target is missing, replace one parent with a carrier or breed an intermediate carrier first. When all targets are covered, the pair is ready for an inheritance attempt, but the child can still receive only part of the pool. Keep the parent names, genders when relevant, and passive lists together in your notes so you can reproduce the setup later.

Read regular, rare, World Tree, and mutation labels correctly

The skill directory separates availability labels because not every displayed passive enters a breeding project in the same way. Regular skills are found in the standard Pal pool. Rare or restricted skills may require a particular acquisition method or species. World Tree passives belong to the new World Tree category and often combine a strong benefit with a drawback. Mutation passives are associated with mutated offspring. These labels describe where the current game data places the skill; they do not, by themselves, prove that every labeled skill can be inherited through an ordinary egg.

Treat a World Tree or mutation label as a prompt to verify the actual individual in your Palbox. If the parent visibly carries the skill, you may record it in that parent’s pool and use the planner to check coverage. If you have not obtained a carrier, do not assume the skill can be created by combining unrelated parents. The directory is intentionally conservative about eligibility and odds. It shows the skill name, rank, effect, and source class that can be checked in the pinned version 1.0 data, while inheritance probability remains unavailable until supported by reproducible evidence.

Use cakes as game choices, not as made-up multipliers

The version 1.0 changelog gives players several cake choices. Special Cake increases the chance of inheriting multiple passive skills from the parents. Deluxe Vegetable Cake increases the likelihood of mutation and makes stat growth more likely. Mushroom Cake slightly increases the likelihood of higher stats, while Vegetable Cake produces two eggs at once. Those statements are useful when deciding which resource to spend, but they are not a public probability table. A planner that turns “increases” into an arbitrary percentage would create false precision and could mislead a long breeding project.

Choose the cake that matches the current bottleneck. If the correct species is easy to produce but the child repeatedly misses parent passives, Special Cake is the relevant official option. If the goal is a mutation, Deluxe Vegetable Cake is the option explicitly connected to mutation likelihood. If throughput matters more than a particular inheritance event, producing two eggs may be useful. Record which cake was used when comparing attempts. Without that note, a small set of observations cannot tell you whether two parent setups behaved differently or simply used different breeding items.

Keep the species route separate from the passive route

The breeding calculator answers which child species a pair produces. The passive planner answers whether the desired traits are represented in the entered parent pools. Run those checks in that order. First confirm that the exact parents produce the target species in version 1.0, including any variant or gender condition. Then enter the individual passives on those parents and inspect target coverage. A pair can be correct for species and poor for traits, or excellent for trait coverage and wrong for the intended child. Combining both questions in one unqualified score would hide that distinction.

For a longer route, decide where each target passive enters the chain. An intermediate child can become a carrier for a later step, so save its actual passives rather than assuming the planned set appeared. If an intermediate loses an essential skill, either breed that step again or choose another carrier before continuing. The shortest species chain is not always the easiest inheritance chain. A route with one extra species step may let you reuse a prepared parent with two important passives, reducing the number of separate trait pools you need to maintain.

Turn each hatch into a useful breeding record

A simple breeding log makes the planner more valuable. Record Parent A, Parent B, their visible passives, the cake, the resulting species, the child’s passives, whether a mutation was shown, and the game build. Keep failed eggs in the record as well as successful ones. Selective notes that include only the best outcome cannot support a probability estimate. Even with complete notes, a personal sample may still be too small for reliable odds, but it can reveal input mistakes, such as using the wrong variant or replacing a prepared carrier with another individual of the same species.

Recheck the page’s data date after a hotfix. Skill effects, labels, and breeding rules can change independently, so a saved target list should always be interpreted against the current game build. If the in-game description differs from this directory, report the skill name, exact wording, platform, language, and build. That is enough to investigate the data without requesting account credentials or an entire save file. Until a verified probability model exists, the safest workflow remains straightforward: confirm species, confirm parent coverage, choose the relevant cake, and inspect every child.

Frequently asked questions