Back to blog

Palworld 1.0 Changed Your Old Breeding Combos — Here Is What They Make Now

1.0 re-ranked the breeding table, so old combos still hatch — they just hatch the wrong Pal. Three combos the community reported broken, checked against the 1.0 game files, plus how to spot the rest.

Jul 17, 2026PalRoutePalRoute

If you came back for 1.0 and a combo you've used for two years suddenly gives you the wrong Pal, you're not doing anything wrong. The recipe didn't get deleted — the numbers underneath it moved.

That's worse than a combo simply being removed, because it doesn't fail loudly. You still get an egg. You still wait for it. It just hatches into something else.

Three combos the community reported, checked against the 1.0 files

Old comboUsed to makeMakes now
Bushi + PenkingAnubisSibelyx
Orserk + GrizzboltAstegonSilvegis
Lunaris + PaladiusSelyneRelaxaurus

Each of these came from a player reporting it had stopped working. In every case the pair still breeds fine — it just lands somewhere else entirely now.

Why this happens

Palworld doesn't store a recipe per Pal. It takes the average breed power of the two parents and finds the Pal sitting nearest to that number (with a tie-break when two are equally close). 1.0 changed the breed power of the returning Pals, so every combo that depended on those numbers quietly moved.

Bushi + Penking is the clearest example:

PalBreed power
Bushi1560
Penking2070
Midpoint1815
Sibelyx1810
Anubis480

The midpoint lands on 1815, which resolves to Sibelyx at 1810. Anubis is all the way down at 480 — nowhere near it.

(If you're checking the math: Xenovader at 1820 is exactly as far from 1815 as Sibelyx is. That's a genuine tie, and the game's tie-break resolves it to Sibelyx.)

Nothing about that pair is broken. Anubis simply isn't what sits at the midpoint anymore.

Worked example: so how do you get an Anubis now?

Anubis is the one people ask about most, so it's worth following all the way through.

It wasn't locked to same-species breeding — it still has 234 parent pairs, 179 of which have both parents wild-catchable. Sorted by the level at which both parents become obtainable:

ParentsBoth catchable from
Dualith + Blazamutlevel 46
Suzaku Aqua + Lyleen Noctlevel 49
Whalaska + Lyleen Noctlevel 49
Shadowbeak + Blazamutlevel 50
Gildane + Lyleen Noctlevel 53

Dualith + Blazamut is the earliest, and both spawn wild from level 46. That's the honest floor — the easy early Anubis routes really are gone.

And here's the part most guides skip: Anubis spawns wild at levels 55-80. So breeding buys you about 9 levels, not 30. If you're already near 55 and you just want an Anubis, go catch one. Breeding is worth it when you want specific passives on it — that's what the pen is actually for now.

One more that comes up a lot: Ghangler Ignis + Lyleen → Anubis does work. But it isn't the cheap option people assume — Ghangler Ignis has no wild spawn at all, so you'd have to breed that first.

The full list of all 234 pairs, with each parent's wild level, is on the Anubis page.

How to check the rest of your combos

The pattern holds for anything you remember from before 1.0: it probably still produces an egg, and that egg is probably not what you expect. If a combo you trusted has gone quiet on you, look it up fresh rather than assuming it was removed — most of them weren't removed, they moved.

The Pals that genuinely can't be bred from a mixed pair anymore — the tower bosses and the legendaries — are a separate change, and they're listed in the breeding guide.

Where these numbers come from

Every number above is read from the Palworld 1.0 game files, by way of the PalCalc dataset (MIT) — breed power and the unique-combo table are extracted from the game's own data, not copied from a wiki.

One honest caveat: the combo table is the breeding formula applied across all 44,851 possible pairs. It tells you which child a pair produces, and it's only as right as the formula and the extracted numbers are. It can't tell you that the game has forbidden a pairing outright. If you hatch something that contradicts a combo here, we want to know — hatch reports are the only way to catch that kind of error.