Start a build with a move you can evolve, then keep a second damage option for its weak matchups. These are source-based build routes, not measured survival-time records.
Four routes to start with
| Starting move | Example partner | Required stat | How to use the route |
|---|---|---|---|
| Ember | Charmander | Power (atk) | Improve the projectile and take its attack stat prerequisite; watch Fire-resistant enemies. |
| Bubble | Piplup | Sprint (spd) | Use the movement upgrade as both a prerequisite and a positioning aid. |
| Razor Leaf | Treecko | Reflexes (cd) | Work toward the cooldown prerequisite while improving the starting attack. |
| Confusion | Psyduck | Reflexes (cd) | Use a Psychic opening, then keep a damaging alternative for poor matchups. |
No matches. Try another name or reset the filters.
A repeatable upgrade order
- Check your starter’s actual starting move in the starter table. Two partners of the same type can start with different moves.
- When offered, take the stat card required by that move’s evolution. The condition is taking it in the current run, not buying an unrelated permanent improvement.
- Raise the move to its maximum level. Choose the golden evolution card when it is offered.
- Add another damaging move from your partner’s type pool or the shared Normal pool. Select it when the matchup or attack pattern makes it more useful.
Tradeoffs that change your decisions
An attack’s raw damage does not account for missed shots, travel, area coverage or enemy resistance. Do not compare a persistent aura and a projectile as if damage divided by cooldown measured identical things.
Melee moves require closer positioning. The snapshot includes a melee balance change in the move definitions, so older tables may disagree with this reference. Inspect both the current move and the risk of staying in range.
Stat upgrades, terrain and weather can change a run. Treat the routes above as starting plans and use the type calculator when your damage seems unexpectedly low.
Sources & snapshot scope
Reviewed 2026-10-15. Mechanics and data refer to the local source snapshot b297089; later live changes may differ. Source inspection is separate from gameplay testing.