A passive is only valuable when it fits the Pal’s job. Compare four-trait builds for work, combat, traversal, and specialist roles.
Define “best” by the job being performed
There is no single four-passive answer for every Pal. A base worker values different effects from a combat attacker, and a traversal mount can care about movement behavior that contributes little at a workstation. The planner therefore selects a role first and looks up a Pal-specific compiled template and role fit instead of sorting passives by one universal score.
The role selector can expose trusted tier and rank data for the target. Template details describe the named build, its passive set, aggregate effect, acquisition stage, confidence, alternatives, and caveats when those facts are available. If the catalog has no compiled build for that Pal-role combination, the page says so and keeps the four slots editable.
- Choose the actual assignment
Start with the target’s intended work suitability, combat purpose, traversal type, or specialist task rather than a generic popularity list.
- Review the exact template
Read the four listed passives, alternatives, acquisition stage, and caveats; confirm that the evidence matches your game stage and use case.
- Map the traits to carriers
Accept, replace, or decline each slot, then select the exact roster copy that owns every trait you plan to transfer.
Use fallbacks without disguising them as ideals
Some top traits may be unavailable at your progression stage or absent from the current roster. Compiled alternatives provide relevant substitutions where the data supports them, but a fallback is not silently relabeled as the exact ideal. You can also replace a slot manually when your build values survivability, convenience, or availability more than the documented maximum.
Role quality and breeding effort remain separate. Make results rank trusted role facts first and use breeding distance as a tie-breaker; they do not declare a weaker role fit “best” merely because it is one generation closer. That separation helps compare a near-term practical project with a longer endgame project without merging the two judgments.
Named four-passive builds in the compiled templates
The compiled Maximum Work Throughput template uses Demon’s Hand + Remarkable Craftsmanship + Artisan + Work Slave. The 24-Hour Production template replaces Work Slave with Vampiric to support overnight operation, while the Breeding Parent template uses Philanthropist + Babysitter + Insomnia + Mastery of Fasting. Those are complete named four-passive targets from the pinned recommendation data, not generic placeholders.
For combat, the template changes with element: the Fire Combat set uses Flame Emperor + Demon God + Serenity + Musclehead, while other elemental sets replace the elemental trait and keep the shared combat core where the compiled data says it applies. Open Full custom to replace any slot, then select the exact roster copies that actually carry the chosen traits. The passive calculator turns the template into real carrier lines and preserves entered baggage.
- Natural work level is a major part of worker fit; passives do not erase the target Pal’s underlying suitability.
- Traversal recommendations are role-specific and should not be assumed to improve combat or workstation output.
- Partner Skills, souls, condensation, research, handbooks, food, and base geometry may change practical results outside the compiled ranking.
Recommendation limits matter as much as tiers
The app does not simulate every damage formula, movement surface, food break, raid, facility queue, or patch-specific interaction. A tier and rank summarize the compiled role model and its stated caveats; they are not proof that one Pal will outperform another in every player’s base or combat setup.
Passive availability and balance can also change with game updates. Recommendations are tied to the pinned data revision and known passive definitions. Use the current game to verify newly changed effects, and treat a custom four-slot build as a deliberate override when your priorities differ from the model rather than as an error in the planner.