Data & editorial methodology

Pal records, base stats, elements, work suitability, skills, standard drops, breeding combinations, recipes, Technology unlocks, vendors, loot pools, Ranch rows, world placements, spawn groups, and field bosses come from the normalized v1.0.0 export.

Pages call these facts extracted, recorded, or game-table backed. A present table row proves that the row exists; it does not prove every runtime condition surrounding it.

PalMods combines extracted rows to answer useful questions: earliest mapped wild level, expected item yield, the densest recorded spawn cluster, available acquisition routes, and breeding paths from mapped starters.

Derived values identify their inputs near the result. They are reproducible calculations, not a claim that one route is always fastest for every player or world setting.

Advice about terrain, fight execution, real travel time, respawn timing, reliability, or subjective “best” choices needs a named source, an explicit gameplay check, or wording that makes the limitation clear.

If the current extraction cannot verify a claim, PalMods leaves it unknown or labels the supporting source. We do not turn community repetition into a “verified” fact.

Spawn-marker counts are not spawn-rate measurements. Loot weights describe the exported pool, not a guarantee for one chest. Static resource placements do not reveal respawn time. A legal item row without an acquisition reference may be unavailable, reserved, or connected through a system outside the normalized inputs.

Those distinctions are why PalMods uses phrases such as “mapped,” “recorded,” and “in the current export” instead of overstating certainty.

Every indexable Pal, item, skill, breeding, and work entity receives a deterministic content fingerprint. Its public update date changes only when its underlying SEO-visible data changes. Rebuilding or redeploying unchanged data does not make every page look new.

Dataset releases compare those fingerprints and notify search engines only about added, changed, or removed URLs. Search-engine notification is a discovery signal, never an indexing guarantee.

1. Extract and normalize the current supported game build.
2. Validate schema, record counts, identifiers, references, and route invariants.
3. Regenerate summaries, maps, guide answers, and entity fingerprints.
4. Run unit, server-render, sitemap, TypeScript, and production-build checks.
5. Publish the changed pages and monitor real search/indexation results.