Where do these numbers come from?
From the committed dataset diff for each version pair — the same file the per-version page reads. Nothing here is a summary of a patch note, and a pair with no built diff shows no counts rather than zeros.
Palworld version changes
Checked against Palworld v1.0.3 · verified 2026-08-25 · dataset 2026-08-12-29cd766c · Data status · Sources · Methodology
This site answers for 2 Palworld versions, and tracks 730 recorded differences between them. Each row below links to the page that says which published build verdicts changed, how many became legacy-only and how many became newly obtainable. Every count is derived from the committed dataset diff for that version pair — not from reading the patch notes.
- Versions answered for
- 2
- Version pairs with a built diff
- 1
- Recorded differences
- 730
- Current dataset
- 2026-08-12-29cd766c
Palworld v0.7.0 → v1.0.3
730 recorded differences · diff built 2026-08-12
- breeding pairs added
- 212
- acquisition rules added
- 149
- breeding pairs removed
- 146
- items changed how they are obtained
- 93
- Pals added
- 72
- skills no longer learnable
- 25
- skills learnable
- 13
- fixed passives added
- 13
- acquisition rules removed
- 6
- mechanic rules changed
- 1
807 published build verdicts answer differently: 172 became legacy-only, 635 became newly obtainable, across 299 Pals. See which ones.
Palworld version changes FAQ
Does a new Palworld version change my saved build?
It can. A build that was obtainable in an earlier version may become legacy-only, meaning no current route reaches it and it can only exist on a Pal that already has it. The per-version page lists exactly which published verdicts moved.
How quickly does this site follow a new version?
A scheduled watcher notices a new version and opens an intake issue; nothing is ingested automatically. A person reviews the patch, the dataset is rebuilt and checked, and only then is it promoted — so the site keeps answering with the previous dataset until that finishes.