Palworld planning handbook: check a task in your own save
On this page
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.
Start with the installed build
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.
Make a useful comparison
Work through one reachable objective at a time. Check the supplies needed for a short outing, then return and record what changed. Do not treat an online route written for another build as a promise that the same item or encounter exists.
Keep the limits explicit
Before expanding, compare what you actually spend with what you collect. Keep one small task as a test rather than changing production, equipment and travel plans simultaneously.
A record you can check later
Write the platform and build, the task or encounter, the input you changed and what you observed. Include the relevant help text or announcement if it supports the result. Leave unobserved fields blank. This is an editorial method for keeping useful notes, not a claim of first-hand testing by Luminesca.
Open the party notebook to keep observations locally. It uses your entries and does not import our retired species dataset. Review the build before reusing an old note.
Sources and scope
Official store description · Developer update index. The store provides general product context and the update index leads to developer announcements. Neither is used here as proof of a species-specific recipe, spawn, drop or statistic.
Achievement planning: use the platform list for your build
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.
Keep progress notes beside the requirements you can actually see. A hidden achievement or an untested trigger should stay unknown until supported, not be filled with a guessed route.
Before a long run, check any prerequisite you have already completed and whether the save can be recovered. The former fixed achievement total and untested unlock instructions have been withdrawn.
Advanced Tips
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.
Change one part of the process and record the outcome. A result is easier to interpret when the build, settings and inputs are unchanged. Avoid presenting an unexplained improvement as a universal exploit.
A technique mentioned in an update or a community post may have been changed or may depend on modifications. Check the relevant release note and try a recoverable test before relying on it.
Base Building
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.
Keep a before-and-after note when changing the layout or worker. Check whether the task starts, whether items arrive and whether the output is usable. A changed production rate can have several causes.
Compare a general-purpose worker with a specialist using the same task and settings. Record only what the installed build shows; the retired work-suitability dataset is not used by our notebook.
Breeding combinations: how to document a tested pair
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 in-game information and a repeatable observation to decide whether a pairing is useful. A copied table without its version and method cannot establish what will happen in your own save.
Our previous fixed recipe list has been withdrawn. This page provides a recording method; it does not supply replacement recipes or calculated outcomes.
Breeding & Passives
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.
Keep the observed result beside the parent pair and build information. Do not combine species results, inherited traits and random variation into one promise.
If you want to repeat a result, establish which parts the game documents and which parts you only observed once. Our former recipe and passive tables are withdrawn until their entries have usable evidence.
Catching System
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.
Compare attempts only when the conditions are similar. A small set of successful attempts does not prove a universal probability; do not turn an anecdote into a guaranteed capture method.
Separate a defeat drop, a capture outcome and a base-production item in your notes. They are different observations and should not be copied into one universal drop field.
Bosses & Combat
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.
Use an attempt to identify one problem, such as positioning, recovery or an equipment requirement. Change one relevant part of the plan and compare the result rather than replacing the entire party after every attempt.
A recorded element label is not a complete measure of damage. Level, equipment, attacks and settings can matter; do not treat a type count as proof that a boss is covered.
Mods & Platforms
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 a recoverable copy where the platform permits it and follow the author’s actual uninstall and restore instructions. A download being popular does not prove that it is safe or appropriate for your save.
For a multiplayer group, agree which modifications are permitted and verify the host’s setup. We do not link an unverified mod download or claim that a modification works across every platform.
Multiplayer & Servers
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.
Agree who maintains the world and how changes are communicated. Before an update, establish the host’s backup and restart procedure; do not assume a platform service and a self-hosted server behave identically.
Test the required connection before committing a group evening. Keep credentials and private server addresses out of public notes and shared exports.
Raid preparation: check the current summon and encounter
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.
Check the consequences of starting the encounter in the current world and make a recoverable preparation where the platform permits it. A party recommended for one setting cannot guarantee another result.
Record the actual attempt and the one change you would make next. Keep the observations separate from an assumed drop table or a universal damage threshold.
Resource routes: build a map from confirmed observations
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.
Compare the route with the supplies and craft you intend to complete. A shorter line on a map may involve a different access requirement; record the full return as well as the outward trip.
The earlier fixed deposit and spawn claims have been withdrawn. Use the resource planning guide to distinguish map pickups, drops and production before combining their results.
Resources & Economy
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.
Cost a craft using the recipe shown by the installed build. Include the trip or production effort you actually need rather than relying on an unsupported hourly output figure.
Choose a repeatable small route or production task and note its conditions. A result from one location does not establish that every copy of a species drops the same item or works in a ranch.
Tech Tree & Crafting
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.
Choose the next unlock from a problem you actually have: a missing input, a transport limitation or a tool you cannot yet craft. A long list of every unlock is less useful than identifying the current dependency.
Compare resource use for one production cycle. Keep equipment changes and world settings in the notes so that an old cost estimate is not mistaken for a current recipe.