What does "validated" mean on this page?
passed — the dataset passed the integrity, referential-consistency and per-family coverage checks the build runs before any page is allowed to publish.
Checked against Palworld v1.0.3 · verified 2026-08-25 · Data status
The live dataset behind this site is Palworld v1.0.3, validation status passed, with claims last verified 2026-08-25. It covers 299 Pals and currently supports 1322 published pages, each traceable to a graded source rather than to an unverified guess.
| Version | Pals | Parent pairs | Same-species-only | Passives | Active skills with a route | Obtainable Skill Fruits | Pal locations known |
|---|---|---|---|---|---|---|---|
| v0.7.0 | 227 | 25878 | 15 | 92 | 235 of 235 | 89 | 0 of 227 |
| v1.0.3 (current) | 299 | 44850 | 26 | 115 | 312 of 320 | 91 | 118 of 299 |
"Active skills with a route" counts the skills the engine can say something about — the ones reached by a learnset entry, an obtainable Skill Fruit or a verified acquisition rule. The second number is every active skill in the dataset. The difference is skills that exist with no verified way to get them on any Pal; they are listed on the all-active-skills page and answer "needs verification" rather than "no".
"Pal locations known" is a hard limit of the source, not of this site: the wiki's location table covers a named-area spawn for some Pals and nothing for the rest. A Pal profile shows a "Where to find" section only when a location is known — the other Pals show no such section, never a placeholder or a guess.
A family marked partial means we know our coverage has gaps, and the engine answers "needs verification" instead of "no" for anything that depends on it.
| Family | v0.7.0 | v1.0.3 |
|---|---|---|
| breeding | complete | complete |
| passives | complete | complete |
| active skills | complete | complete |
| learnsets | complete | complete |
| items | complete | complete |
| mechanics | complete | complete |
Species exclusivity for active skills is not populated: no source we have pinned exposes the flag. The engine supports the rule, and no active-skill page has been frozen while it is open. Where exclusivity would have been the reason, the answer still comes out correct through the other channels — with a less precise explanation.
Historical coverage is one version deep (v0.7.0). A build that was only obtainable before that has no dataset to prove it, so it answers "needs verification" rather than "no".
passed — the dataset passed the integrity, referential-consistency and per-family coverage checks the build runs before any page is allowed to publish.
2026-08-25, against the v1.0.3 dataset generated 2026-08-12. That date is the same freshness stamp shown on every published page.
The engine answers "needs verification" instead of "no" for anything that depends on it, rather than guessing — see the completeness table below for exactly which families are affected.