Version before volume
A page names a game or package version only when its underlying dataset carries that version. Regeneration alone does not make a page current.
Data methodology
How Palpedia earns trust, one field at a time.
A practical explanation of where the data comes from, what each page can promise and where Palpedia deliberately stops short.
01
Source map
Every category has a source, a scope and a freshness signal.
The database is not one undifferentiated block of truth. These are the source classes behind the current reference.
| Area | Current source | Coverage | Freshness shown |
|---|---|---|---|
| Pals | Local Palpedia Palworld 1.0 catalog and portrait manifest | 299 entries; 139 include legacy narrative detail and 160 use core stats only | Version and data status per profile |
| Items | Installed official-game-data extraction | 1,891 records with recipes, stats, unlocks and provenance where present | Dataset generated 2026-08-03; package 1.10.619.0 |
| Structures | Installed official-game-data extraction | 487 records with construction, technology and base fields | Dataset generated 2026-08-03; package 1.10.619.0 |
| TCG | English Palworld Official Card Game catalog | 242 cards and 4 product groups | Retrieved 2026-07-29 |
| Capture Lab | Illustrative local formula configuration | Demo scenarios, not official capture rates | Labelled as a demo on the page and in metadata |
02
Data contract
The rules that keep a reference page useful.
Missing stays missing
Missing locations, skill narratives, prices or drop rates are disclosed instead of inferred. Tool assumptions live beside the tool.
Identity stays stable
Each indexable entity receives one clean URL. Duplicate item names remain separate records with their official IDs.
Structured data follows the page
Schema types describe what the visible page actually contains: entities, tools, guides and breadcrumbs are not inflated into commercial offers.
03
Boundaries
What this methodology does not claim.
Palpedia is an independent fan reference. Installed data can contain unused or internal records, editorial guides can age and search visibility is never guaranteed.
Revenue claims, official status and unavailable facts are not manufactured for SEO. A correction should identify the URL, field, expected value, supporting source and game build.