Start with the Pals you can reproduce, decide what the target should do, select four desired passives, and follow the resulting tree.
Keep the roster simple and add traits only when needed
A useful roster answers one fast question: which Pal species do you own? That compact pool defines broad species reachability and keeps roster entry responsive even for large collections.
When traits matter, the selected planning mode asks only for the relevant carrier Pals. The planner stores this data locally and does not require a game-save upload or account.
- Build an honest roster
Select each species you own once; do not catalog every individual Pal before planning.
- Choose species or trait planning
Use Quickest path for a target without traits, Start to target for one existing trait stack, or Full custom for traits split across several Pals.
- Breed, record, and recalculate
Follow available stages, record useful offspring in the plan, and regenerate the remaining route when a hatch or access assumption changes.
Learn the three planner modes
Quickest path finds a legal species route with the fewest sequential breeding generations found by the bounded search from the current roster and ignores traits. Start to target moves the traits already together on one selected Pal. Full custom starts from role suggestions and four editable trait slots, then searches for a route that consolidates the carrier Pals you confirm.
The modes are not quality levels. A quick species path may ignore the one parent that owns your desired passive, while a passive-aware custom tree can require more operations. Start to target can also be longer because preserving the chosen ancestor is the point. Decide which constraint matters before comparing step counts.
Worked walkthrough: from worker goal to route
Suppose you want a target for a specific base job. Filter reachable Pals by that work suitability, compare compiled role tier and rank, and open the chosen target. On Build, inspect the template, replace traits that do not fit your available game stage, then identify the real carrier for each trait before generating the plan.
- Use Tree view to understand parent-child dependencies and the origin of each intermediate species.
- Use Rounds view to see which independent stages can be attempted concurrently without assuming identical hatch times.
- Use “I do not have this” to exclude a proposed route input temporarily, then restore it later without rewriting the roster.
Interpret checkpoints, bridges, and warnings
A retained-passive label tells you what a successful offspring should keep for downstream breeding. A sex checkpoint tells you a later pairing needs compatible parents but cannot predict the hatch. A zero-passive bridge connects species outcomes and is not considered a desired-trait source. Baggage warnings reflect the complete passive lists entered for selected carriers.
The planner verifies its modeled recipe graph but cannot guarantee inheritance, an egg count, or minimum elapsed time. Incubation settings, cake supply, capture effort, breeding-pen capacity, random passives, and real-world execution remain outside the calculation. A pruning warning also means the displayed legal route was found without exhaustively comparing every alternative.
Keep saved plans aligned with real progress
Save a route when you want a stable checklist, but update the roster when the world changes. Recording a successful hatch gives future searches a real exact carrier and can eliminate completed ancestry. If a copy is deleted or loses a required trait in your records, a saved build can become blocked rather than silently assigning a different parent.
The bundled catalog and graph target a pinned game revision, so combinations or recommendations may lag a later patch. Export the local roster for backup before clearing browser or app storage. Use the planner to organize decisions, then verify patch-sensitive facts and actual inheritance behavior in the version you are playing.