Editorial correction: October 6, 2026. Unverified species fields, spawn claims and blanket version labels have been withdrawn. Official store description · Developer update index. These links establish product and update context, not every mechanic or field in a save.
Choose a current task, inspect the information in your installed game and keep a note you can reproduce. This collection now separates planning methods from species data that could not be supported. It does not claim a complete Pal roster or a patch-tested walkthrough.
Choose the save and settings before planning a route. Record the platform, displayed build and any world settings that affect your session. Use the in-game tutorial and help for the mechanics present in that build.
Inspect the target and the capture information your game actually displays. Record the equipment used, the target condition and any relevant world settings. The old five-rank species table has been withdrawn.
Start with a single task your base is failing to complete. Observe the station, inputs, output space and the assigned worker rather than selecting a Pal only from an old ranking.
Record the parent pair and any requirements shown by your build before spending resources. An outcome from a different version or modified server is not evidence for a guaranteed recipe in your save.
Use the recipe and technology requirements displayed in your own game. Write down prerequisites, required resources and the station used before deciding which unlock to pursue.
Record the encounter name and conditions visible in your build. Check your own equipment and the labels or help the game gives for attacks and resistances; our notebook does not calculate a guaranteed matchup.
Record where and how an item was obtained in your save. Separate a world pickup, an encounter drop and an output from a base task. The previous dataset incorrectly used one field across these different conditions.
Define what you want to improve before choosing a method: time to craft, supplies per outing or a particular encounter. Keep a simple baseline under the current world settings.
Ask the host which platform, build, world settings and modifications the group is using. Verify the current connection and server instructions through the game or official support rather than copying an old capacity claim.
Treat a modification as a separate dependency with its own author, supported build and installation instructions. An official game update does not establish that a third-party modification is compatible.
Use the developer update index to locate the release note for the change you are investigating. Record its title, publication date and the build it names. The previous site-wide v1.0 stable label has been removed.
Start with the achievement list visible on the platform you use. Record the displayed title and description rather than assuming a fixed total shared by all platforms.
Record both parents, the installed build, relevant settings and the observed offspring. Keep inherited traits in a separate note so that a species outcome is not mistaken for a guaranteed trait result.
Use the map and markers in your installed game to record a location you actually reached. Include the item, access conditions and build rather than publishing a guessed coordinate.
Use the encounter information displayed in your build to establish the required item, location and conditions. The earlier fixed raid roster and untested recipe claims have been withdrawn.
Paldeck verification guide explains what to record in a species entry. The party notebook records your own observations, with explicit local save and export. It does not fill missing fields with guessed statistics.
On October 6, 2026, we consolidated the old species detail pages, removed their unsupported ranch and drop statements and withdrew the shared dataset. Fixed version, achievement and recipe claims were removed from the related planning pages. Old species addresses now redirect to the verification guide.