Palworld Mutated Eggs: What Is Confirmed, Observed, and Still Unknown

Keep species results separate from egg outcomes

A breeding calculator answers a species question: which child is recorded for two parents? A Mutated Egg question is different: what additional outcome, trait or passive can appear after that species result is set. Mixing those two layers is the fastest way to turn a useful route into a misleading probability claim.

Players are actively comparing egg batches, Cake choices and hatchery behaviour. Those observations are valuable for finding questions to test, but they are not automatically official rates or rules.

Use an evidence label for every claim

For this topic, label a statement as Confirmed when it appears in official notes or can be directly reproduced, Community observed when several player reports describe it but the rule has not been published, and Unknown when a rate or interaction has not been verified. This is more useful than publishing a confident-looking percentage with no method.

For example, a player can report a Mutated Egg from a breeding batch. That supports the observation that the event happened in that setup; it does not establish the global chance, whether every Cake modifies it, or whether one hatchery interaction applies on every platform.

A practical test log for your own breeding run

If you want to learn from a large egg batch, write down inputs before hatching. Keep the parents and location consistent, note any Cake or hatchery choice, count every egg, and separate duplicate eggs from mutation outcomes. A small, clean log is more useful than a large memory-based estimate.

• Record the exact two parents and game build.
• Record the food or Cake used for each batch.
• Track total eggs and visibly mutated eggs separately.
• Record hatchery type and any relevant partner skills.
• Do not combine results from different patches without a clear label.

Are mutation outcomes fixed, and can exclusive passives be inherited?

Players are currently testing whether a Mutated Egg resolves from a fixed candidate pool and whether mutation-exclusive or World Tree passives can move through later breeding. Those are two separate questions: the egg's species outcome and the passive carried by the hatched Pal do not have to follow the same rule.

Current community reports are useful test leads, but they are not enough for PalBreed Lab to publish a complete candidate pool or a guaranteed inheritance rule. Until the current build is reproduced against a versioned dataset, record the source Pal, both parents, the resulting egg and the passive separately. This prevents one successful hatch from being presented as a universal recipe.

What PalBreed Lab should and should not promise

PalBreed Lab can show the verified parent route for the base species. It should not promise an exact mutation rate until that rate is supported by a current, reproducible source. When a feature is implemented, community observations should remain visibly separate from confirmed data.

That distinction protects players who are planning a long breeding session: a route can be accurate even when the probability of an additional egg outcome remains unknown.