Instead of scrolling every theoretical pair, select the Pals you can access and see the useful targets those combinations unlock.
Turn a pair database into reachable choices
A breeding combination is useful only when its parents or prerequisites are available. The planner loads a pinned graph of canonical species outcomes, starts from the renewable roster, and repeatedly adds legal children. That reachability pass lets the Make page show direct combinations beside multistep targets without pretending every catalog recipe is immediately available.
The result card shows whether the species is already owned, direct, or multistep, plus its generation depth and recipe-operation count. Filters can focus on a name, Paldex number, work suitability, maximum generations, or new species. Role ranking stays visible so an easy combination is not automatically presented as the strongest worker, fighter, or mount.
- Define the available pool
Mark each species you own once. Specific passive carriers are added only inside a trait-aware plan.
- Browse reachable outcomes
Use Quickest path to enumerate what the current pool unlocks at the lowest generation depth found, then narrow the list without altering the underlying roster.
- Verify the ancestry
Open a promising result to see the witness recipes, bridge species, operations, and dependencies before collecting cake or assigning breeding pens.
Combination modes answer separate questions
Quickest path asks for the legal species route with the fewest sequential generations found. Start to target asks how to move one exact Pal and its selected traits onto a target. Full custom begins with a target and up to four passive slots, so its route may consolidate several trait carriers even when another species-only route has fewer generations.
These modes can disagree without either being wrong. For example, two renewable parents might make a target directly, while a valuable limited carrier needs a bridge chain to deliver Legend. The direct combination solves species access; the longer custom route solves the requested build. Pick the mode from the constraint you actually care about.
Verified combination examples from the pinned graph
The shipped graph contains concrete species outcomes such as Relaxaurus + Sparkit → Relaxaurus Lux, Kitsun Noct + Frostallion → Anubis, and Jormuntide + Blazamut → Dualith. These are direct examples in the planner’s pinned data pack, not a promise that the same pair remains unchanged in a later game patch. Search the target in Make to see whether your saved roster can supply those parents or a multistep ancestry leading to them.
A direct recipe is only one possible route input. If you do not own both named parents, the solver can still discover the child through other legal pairings or bridge chains present in the graph. If a proposed parent is unavailable, exclude it from the active plan and recalculate. The replacement route may take more generations while remaining a valid way to reach the same target.
- Maximum generations limits route depth; it is a display and reachability constraint, not an estimate of eggs or elapsed time.
- Work suitability filtering checks the target’s natural work data and does not score your base layout, food supply, or research bonuses.
- Difficult legal routes remain visible when filters allow them, while truncated searches carry an explicit comparison warning.
Combination data is pinned, not omniscient
The app does not scrape a live wiki or query a game server each time you search. It uses the catalog and breeding graph shipped with the current data pack, excluding synthetic or noncanonical entries from ordinary roster selection. That makes results reproducible, but a newer game patch can make the bundled graph stale until the data is updated.
A verified combination proves the modeled species outcome, not passive odds, offspring sex, incubation time, or practical acquisition cost. The route can identify missing bridge species and checkpoints but cannot catch them for you. When real access differs from the plan, remove the proposed input for that route and recalculate rather than forcing an impossible checklist.