How 97.7% of Palworld breeding recipes silently changed in 1.0 — and how to find what yours became

Curtain — Tue, 21 Jul 2026 15:39:26 +0000

You followed an old breeding guide. You put Penking + Bushi into your breeding farm, dropped the cake, waited for the egg... and out hatched Sibelyx, not the Anubis the guide promised.

You're not alone. Your guide isn't broken. The recipe changed.

When Palworld hit 1.0, the breeding table got quietly rewritten. Almost every pairing that players had memorized from early-access now produces a different Pal. There's no in-game notice, no patch note that lists the hundreds of changed combos — just a lot of confused hatchings.

So I dug into the data. Here's what I found, and the small tool I built to make sense of it.

What actually changed in 1.0

I compared two snapshots of the game's breeding data — the pre-1.0 set and the current 1.0 release — both sourced from the open-source PalCalc project.

The headline number:

97.7% of comparable pre-1.0 parent pairs now produce a different Pal.

That's not a typo. If you take the breeding pairs that existed before 1.0 and run them against the current data, nearly all of them hatch something new.

A few concrete examples players keep running into:

Old recipe (pre-1.0)	What it makes now (1.0)
Penking + Bushi	~~Anubis~~ → Sibelyx
...	(more pairs in the tool)

The mismatch matters because most breeding guides and calculators on the internet still show the old results. Players follow them, breed, and get confused.

The subtle trap: renumbering vs. real change

There's a detail that trips up every breeding tool that tries to track this.

When Palworld 1.0 launched, it also renumbered parts of the Paldeck (Pal #139 vs #116, etc.). A naive diff tool would see the number change and wrongly report "the breeding result changed!" — when really only the number changed, not the actual Pal.

To avoid that false signal, I match Pals by their internal game name, not their Paldeck number. A renumbering is not mistaken for a changed breeding result. Only genuine recipe changes are counted.

The tool: PalShift

I wanted a dead-simple way to answer one question:

"I remember this old pair. What does it make now? And how do I still get the Pal I originally wanted?"

That's literally the whole product. PalShift — a Palworld 1.0 breeding changes checker.

How it works:

You enter (or pick) an old parent pair you remember.
It shows you what that pair makes in the old data vs. what it makes in 1.0.
If the result changed, it gives you verified current 1.0 routes back to the Pal you originally wanted.

The data is built from public PalCalc snapshots and doesn't call another breeding calculator at runtime. There are dedicated pages per popular target (e.g. Anubis breeding changes) so you can jump straight to the Pal you care about.

It runs entirely client-side, supports English / 中文 / 日本語 / 한국어, and — because it's a fan tool for a game — it's free.

Why I think "the diff" is the interesting part

There are plenty of general breeding calculators out there. Most of them do the same thing: pick two parents, see the child.

But the actual pain point players have right now isn't "what does X + Y make?" — it's "why does my old recipe give me the wrong Pal, and how do I fix it?" That's a diff problem, not a calculator problem. Nobody else focuses on it.

If you've been breeding in Palworld, I'd love to know:

Did a recipe you memorized break on you in 1.0?
Which Pal were you trying to get back?
Are there combos you'd want a "what changed" view on?

The whole thing is open about its data sources — pre-1.0 uses PalCalc v1.17.1, current data uses v1.17.3 (the first corrected 1.0 release line). You can review the PalCalc source yourself.

Unofficial fan-made utility. Not affiliated with or endorsed by Pocketpair.

DEV Community: Curtain

How 97.7% of Palworld breeding recipes silently changed in 1.0 — and how to find what yours became

What actually changed in 1.0

The subtle trap: renumbering vs. real change

The tool: PalShift

Why I think "the diff" is the interesting part