Unofficial fan-made Palworld guide
Plan Palworld base worker passives by role, compare work-speed skills, use PalCalculator planning notes, and avoid guaranteed inheritance claims.
Base worker passives are about role fit, not one universal best list. A mining worker, crafting worker, transporter, and early-game helper may need different priorities.
PalCalculator is an unofficial fan-made Palworld calculator and guide site. Current passive seed data is limited, so use this page as a base-work planning framework and verify recognized passive names and caveats in the passive planner and `/data-sources/`.
Primary CTA: Open the passive planner
Secondary CTA: Find a base-worker route
Open the passive planner: `/passive-skill-calculator/`
Find a base-worker route: `/breeding-route-calculator/`
Open the passive planner · Find a base-worker route
Start with the job the Pal will do in your base. Useful categories include: Work speed and base productivity.
Stamina or uptime where applicable.
Transport and movement utility.
Early-game practicality.
Late-game optimization.
Future breeder value.
Choose base-worker passives by the job first, then check whether the passive names and route plan are supported by the current PalCalculator data.
The current app seed data is limited. Supported passive names such as `Artisan`, `Serious`, and `Swift` can be mentioned as recognized examples, not as a complete best list.
Do not imply PalCalculator currently contains every passive, exact inheritance odds, or a deterministic way to produce the final passive set. Keep `/data-sources/` linked near passive guidance.
For crafting, handiwork, mining, gathering, or similar base tasks, users usually care about work output and time saved. Frame the guidance as planning questions:
What job will this Pal perform most often?
Does the current passive planner recognize the passive names you want?
Is the target Pal practical to breed from your current Palbox?
Are you choosing a short-term worker or a long-term optimized breeder?
If examples are shown, label recognized passive names as examples only. Do not call them a complete or final ranking.
Some base-worker plans care about uptime, movement, or transport behavior. Keep this section goal-based because the current data may not support a complete passive table.
For transport or movement-heavy base roles, look for passive goals that match the job, then verify current passive support in the planner. If the passive name is not recognized, treat it as unsupported for the current dataset rather than assuming the calculator can plan around it.
A perfect passive wishlist is not useful if the target Pal is impractical to reach. Use `/breeding-calculator/` for direct parent-pair checks and `/breeding-route-calculator/` when you need a route from owned Pals.
Choose the base role.
Choose one or two candidate target Pals.
Check direct parent pairs.
If direct pairs are missing, check route options from owned Pals.
Plan recognized passives.
Use IV or stats tools only if the worker's long-term value justifies extra review.
Passive planning does not guarantee inheritance. The page should avoid exact odds, deterministic outcome claims, and “always breed this” language unless reviewed product logic supports it.
Treat desired passives as targets. A supported route can help you reach a Pal, but it does not promise that every desired passive will appear on the next hatch.
The existing passive skills guide explains passive planning across breeding roles. This page is narrower: it focuses on base-work decisions, worker route practicality, browser-visible caveats, and limited passive seed data.
Do not duplicate the broad passive guide's general framework without adding base-specific planning questions and examples.
The best base-worker passives depend on the role, such as work speed, uptime, transport utility, early-game practicality, or long-term optimization. Verify current passive support before treating any list as complete.
No. Current passive seed data is limited. Use recognized examples such as `Artisan`, `Serious`, and `Swift` only as supported examples, not as a complete best-passive list.
No. Passive inheritance can involve RNG and supported-data limits. PalCalculator can help organize a plan, but it should not promise certain passive outcomes.
Start with the base job, then choose candidate Pals and passive goals together. If the target Pal is hard to reach, revise the route or passive plan.
Start with the passive skill calculator, then use the breeding calculator for direct pairs or the route calculator when you need a multi-generation path from owned Pals.
No. They are currently recognized examples in the app data. Do not present them as the full passive table or universal ranking.
This page focuses specifically on base-worker roles, route practicality, and limited passive data caveats. The general passive guide covers broader breeding-passive planning.