Unofficial fan-made Palworld guide
Learn how to plan Palworld breeding routes from the Pals you own, compare missing parents, use route constraints, and read calculator caveats.
Owned-Pal breeding planning starts from your current Palbox instead of one generic chart. The goal is to answer: “Given the Pals I have, what route can I actually try next?”
PalCalculator is an unofficial fan-made Palworld calculator and guide site. Use owned-Pal route planning with visible data-version caveats, browser-local privacy expectations, and no promise that every route, passive, or special combo is supported.
Primary CTA: Open the route calculator
Secondary CTA: Check direct parent pairs
Open the route calculator: `/breeding-route-calculator/`
Check direct parent pairs: `/breeding-calculator/`
Open the route calculator · Check direct parent pairs
Static combo lists usually assume the same answer fits everyone. Owned-Pal planning is more practical because it uses the Pals you already have, the target you want, and the generation limit you are willing to follow.
Use owned-Pal planning when a direct combo is not enough and you need a route that starts from your current Palbox.
Expected inputs should be clear and forgiving: Target Pal.
Owned Pals or current Palbox list.
Max generations.
Optional filters or exclusions where supported.
Current data version and visible caveats.
Add the Pals you can actually use, then choose the target. A larger owned-Pal list can give the route solver more practical options, but unsupported data should still be shown as unavailable rather than guessed.
A missing-Pal note is not always a failure. It may mean the route is possible in the current dataset but requires a parent or intermediate Pal outside your owned list.
Use missing-Pal notes to decide whether to: Catch the missing Pal.
Breed an intermediate first.
Increase max generations.
Add more owned Pals.
Try a different target.
Stop because the route depends on unsupported data.
Shortest route is not always the best route. Compare: Generations: fewer steps are simpler, but not always easier.
Missing Pals: a short route may require a hard-to-get parent.
Practical effort: catching one Pal may be easier than several breeding steps.
Passive goals: a longer route may fit trait planning better.
IV/stat follow-up: valuable candidates may need more review after hatching.
Data caveats: avoid routes that depend on unsupported special-combo assumptions.
Current MVP copy should keep owned-Pal inputs browser-local unless a later owner-approved backend changes that behavior. Do not imply login sync, server-side Palbox storage, or account history if those features do not exist.
Your route inputs are for planning the current calculation. Review the privacy page for current storage behavior before relying on any stronger account or sync assumption.
No route found can be useful information. Try: Recheck the target spelling and selector suggestions.
Add more owned Pals.
Increase max generations.
Remove strict filters.
Compare direct parent pairs in `/breeding-calculator/`.
Review `/data-sources/` for unsupported special-combo or dataset limits.
Do not turn a no-route state into a guessed route. If the current app cannot support a path, the page should say so clearly.
It means planning a route from the Pals you currently have instead of relying on one static combo chart. The route can change when your Palbox changes.
Owned Pals help the route calculator find paths that are practical for your game state and show which parents or intermediates may still be missing.
Current MVP copy should describe owned-Pal inputs as browser-local unless a reviewed backend feature says otherwise. Link to `/privacy/` for the current policy.
Routes can differ because each player has different owned Pals, generation limits, filters, and tolerance for missing parents or longer paths.
No. A short route may require a hard-to-get missing Pal, while a longer route may use Pals you already own or fit passive goals better.
Add more owned Pals, increase max generations, check spelling, relax filters, and review data-source notes. If the dataset does not support a path, do not guess one.
No. Route planning helps with target access. Passive inheritance can involve RNG and supported-data limits, so use the passive planner separately.