Select the parent moves and their levels above to see which recipe takes priority, what the result does and whether the level requirement is met. The finder reads versioned client data instead of assuming that every matching pair follows the standard Pokémon rules.
What a fusion changes in your plan
A fusion replaces its parent attacks with a new attack and leaves room to learn something else. That makes the decision larger than a simple damage comparison. You are changing attack coverage, timing, reach and the future use of a move slot. A pair that feels comfortable before the machine may behave differently after it combines. Read the result description before committing a plan to it, especially when a familiar projectile becomes a concentrated attack or a persistent effect.
The current PokéBonk fusions snapshot contains 106 named outcomes. The finder separates them into signature, reaction, same-type and glitch families. Those families are not interchangeable rarity grades: they describe how the game chooses an outcome. A flashy signature name does not by itself establish that it is best for every situation. Bring a promising parent pair into the build planning tool so you can consider the rest of the equipment and the attacks that will remain after the fusion.
Meet the parent requirement before visiting the machine
The extracted readiness check requires each eligible parent move to reach level 8. This is the actual fusion gate in this snapshot. It should not be described simply as “the highest possible level,” because a held item can extend the ordinary move cap beyond that gate. The finder checks the selected levels against the fusion requirement and tells you when either parent is still short. It does not assume a machine is available just because the recipe itself is ready.
Weather moves, buff moves and moves that are already fusions are excluded from the parent selection. You also need different moves; picking the same move twice is not a valid pair of equipped slots. If an attack you expected is missing from the selector, check its runtime role before treating that absence as a missing recipe. The public move database describes many attacks, but the browser game adapts those entries into its own attack archetypes. The beginner’s guide explains the broader run structure around leveling and interactables, which is useful before trying to optimize a later combination.
Signature pairs are checked first
There are 79 signature recipes in the extracted table. Each names a precise parent pair and is associated with a League Pokémon. The finder matches those exact move keys before considering either type-based family. The runtime lookup does not require the pair to be entered in a particular order. It also does not turn the associated Pokémon field into a separate species restriction in the recipe lookup. Access to the attacks is still a different question from what happens when you possess the pair.
Use the signature filter when you already know the partner you want to play, or search for a parent move when you remember only part of a combination. Each signature card links the parents into the planner at the extracted required level. That link is a planning shortcut, not an assertion that you start a run with the pair fully upgraded. The current build examples can help put a signature into an overall progression route, while the editorial Pokémon rankings provide context about the partner rather than ranking an isolated fusion name.
Reaction pairs come before generic same-type outcomes
The client defines 8 reaction recipes. These match combinations of allowed parent types. Some sides of a reaction accept alternative types, so reading the full pair rule matters. The finder checks the pair in both directions. A reaction can therefore appear even when the order of your equipped attacks changes. Searching by a type shows the relevant cards without requiring you to remember their translated names.
Reaction names and descriptions can refer to status interactions, areas or attack patterns. Do not reduce those descriptions to a single internal coefficient and call it total damage. The number of targets, time inside an effect and enemy conditions can all change how useful the result is in a run. The effective matchup tool helps with the type portion of a comparison. It is still separate from whether a particular reaction’s pattern reaches the enemies that are causing trouble.
Same-type recipes and the MissingNo. fallback
The same-type family has 18 outcomes, covering the types represented by the client. If no signature or reaction has already matched and both eligible parents share a type, the corresponding same-type recipe is used. This order is important: seeing matching type chips is not enough to bypass an exact signature pair. The finder follows the full lookup sequence so you can inspect the result without manually comparing several lists.
When no higher-priority rule matches, the game has a glitch outcome, MissingNo. Its source description explains that it changes into a random type fusion when cast. It is a defined fallback, not a signal that the wiki failed to find a recipe. A random outcome can be interesting to experiment with, but it is not a predictable substitute for a specific coverage plan. If consistency is your priority, compare the fallback with a named pair whose attack behavior you can describe before the run begins.
Why parent upgrades still matter after fusion
PokéBonk fusions inherit modifiers from the parent attacks. The client merges damage, area and several other modifier components, while cooldown modifiers combine differently. A final parent level alone does not record which upgrade options were selected or what their rarities were. As a result, two runs that reach the same named recipe can produce different attack behavior and numerical output. A recipe finder should identify the recipe confidently without pretending to reconstruct information the player never entered.
The resulting fusion has its own ordinary level cap of 5, with the relevant held item adding 1 further level. That differs from the ordinary attack cap of 8. The planner retains these distinct rules. Its current payload does not store the full parent upgrade history, so directly choosing a fused attack does not produce an exact damage preview. Use the calculator overview to understand which parts of a calculation are known and which require additional run state before treating a result as comparable.
Understand the cooldown shown on recipe cards
A recipe card shows the base cooldown after the client’s balance adjustments. This is more useful than copying the number from the first recipe definition encountered in a bundle. The current client applies a separate power table, a shared cooldown adjustment and a further normalization for some recipes. The extraction pipeline follows those adjustments before exporting the displayed value. Hover text retains the full calculated value when the rounded display would hide a small difference.
That value is still a base cooldown. Your attack-speed stat and inherited move modifiers can change the interval in an actual run. Cast behavior can also contain delayed hits, repeated effects or target-dependent behavior. Dividing a descriptive damage number by this cooldown would therefore not establish a reliable DPS ranking. The held-item database is useful when an item affects attack speed or a conditional damage effect, but the comparison should continue to name the assumptions rather than presenting a false universal winner.
Use the finder to prepare a practical route
Start with the attacks you can obtain reliably, then look for a result that complements the rest of your loadout. The most convenient route may come from your partner’s League kit; a more unusual pair may depend on an unlock or a less predictable offer. Keep that distinction in your notes. A plan that reaches its fusion late needs to survive and clear enemies with the parents for longer, so the quality of the path matters as much as the final animation.
Compare what you lose when the parents disappear. A broad attack may have been controlling crowds while a focused attack helped against a particular target. The combined result can change both roles. Consider which new attack you would like to learn in the freed slot, and avoid assuming that the desired replacement will arrive immediately. For seasonal experiments, check the current season guide rather than assuming every event changes the permanent recipe list. The same version label should accompany any recommendation about PokéBonk fusions.
Search, share and keep a patch-specific reference
The search field matches recipe names, descriptions, types and exact parent move keys. The family filter narrows the results further. When nothing matches, clear part of the search instead of interpreting an empty result as proof that the game has no relevant combination. The pair selector is the most direct check when you know both attacks. It produces a single result according to the current lookup priority and clearly separates recipe readiness from access to an in-run machine.
Copy link preserves the chosen parents, levels and filters. It does not publish free text or modify a game save. A saved comparison is most meaningful with the displayed version and build, because both recipes and balance adjustments can change. Our data sources and method explain the client extraction and the difference between a verified value and an unextracted field. Play and confirm the result on the official PokéBonk site; this unofficial finder is a planning reference, not an embedded copy of the game.