Palworld 1.0 Mutation Breeding: Rules, Limits and Planner Support

Mutation breeding is the least documented part of Palworld 1.0. This guide states what the active dataset verifies, what it does not, and how the planner behaves in each case.

What the planner supports today

The active dataset ships in fixture-preview mode and contains no verified mutation rules. Because of that, the planner does not expose mutation controls: a constraint only appears in the UI when verified data backs it. This is a deliberate limit, not a missing feature.

How unknown mutation rules behave

If a target depends on a rule the dataset does not cover, the planner returns an explicit unknown state and links the active data version. It never fills gaps with generated guesses, and it never presents a community report as a verified rule. Community reports are product evidence — they tell us what to verify next, not what is true.

What counts as verified

• A rule enters the dataset only with a recorded source, retrieval date, game version and license where applicable.
• Special and override rules are pinned by golden fixtures that fail the build if the underlying data changes.
• Every published rule links to a human-readable note on Data updates.

A verified example

A verified mutation example will be published here once the data Gate passes one. Until then, this section intentionally stays empty — an honest gap is more useful than an unverified table.

Have a mutation outcome you can document? Contact us with the parents, child, game version and evidence, or check a build in the planner.