Palworld 1.0.3 — What Changed for Builds

Checked against Palworld v1.0.3 · verified 2026-08-25 · Data status

What changed between v0.7.0 and v1.0.3

Between Palworld v0.7.0 and v1.0.3, 807 published build verdicts changed: 172 became legacy-only and 635 became newly obtainable, affecting 299 Pals. Every number here is derived from the committed dataset diff between the two versions, not from reading the patch notes.

Builds that answer differently
807
Became legacy-only
172
Became obtainable
635
New acquisition methods
302
Removed acquisition methods
172
Rows still under review
160
Pals affected
299
Diagram comparing two Palworld versions: builds that became legacy, builds that became obtainable, methods that changed

Which update this is

The numbers above are this site's own reading of the datasets, not a recap of the patch notes. The image below is Pocketpair's own announcement art for the release, and it is here to say plainly which update the counts belong to — nothing on this page is sourced from it.

Pocketpair's own announcement art for the Palworld 1.0 release, two Pals beside the 1.0 title
Pocketpair's own art for the release these counts describe.Source: Pocketpair, Inc. / Official Palworld press materials

Compare versions

This compares one exact build across two versions. It does not plan a breeding session and does not calculate odds.

Open this build in the checker

How this is measured

Both versions are evaluated with the same engine, and a build counts as changed only when its verdict changes. Counts here are derived from the committed datasets, so anyone with the repo can re-derive them. Rows we cannot classify from the data alone are counted as "under review" rather than assumed harmless.

Published pages this changed

Related questions

Where do these numbers come from?

Every count on this page is derived from the committed dataset diff between the two versions — nothing here is a summary of the patch notes.

What does "became legacy-only" mean?

The build was obtainable in the earlier version and, after the update, no current route reaches it — it can now only exist on a Pal that already has it.

Can I check one exact build's before/after status?

Yes — use the compare mode in the Build Legality Checker, pre-filled with v0.7.0 and v1.0.3, to see one specific build's own verdict change.