Build a Rocket team that covers the whole lineup
Turn a Grunt clue or Leader lineup into a practical team. Compare scenario coverage, shield pressure, and replacements before spending Stardust.
The decision to make
Choose coverage first. A team that handles every listed branch is usually a more useful starting point than one that wins a single matchup quickly.
Build a Rocket teamStart with the encounter you actually have
Match the Grunt’s phrase and type, or select the named Leader or Giovanni. Check the lineup reference before choosing counters: a label describes the encounter, but it does not replace the individual Pokémon’s types. Read the combined weaknesses for a slot to find a useful attack type across several possible opponents.
The Poké Ball marker has a separate meaning: it identifies a possible catch encounter. A Pokémon appearing in the battle does not automatically mean you can catch it afterward. Open Rankings beside a catchable Pokémon when deciding whether its evolution is worth building; use the counter simulation when deciding how to win the battle.
Read scenario wins as coverage
Shadow Battle Lab combines the listed choices for all three slots. Imagine an illustrative encounter with two leads, three second-slot choices, and two closers. That produces 2 × 3 × 2 = 12 lineups. A team winning 11 of those has 91.7% modeled coverage.
Worked example: speed or coverage?
| Team | Scenarios won | Modeled time |
|---|---|---|
| A | 12 of 12 | 55 seconds |
| B | 11 of 12 | 42 seconds |
Choose A when the later slots are unknown and avoiding a retry matters. Consider B only after checking its failed branch and deciding that the risk is acceptable.
Coverage is not the probability of your next live win. The lineup branches are tested as listed; the tool does not know their actual encounter frequencies, your tapping, or whether a rotation has just changed. If the in-game opponent differs, the old scenario result no longer describes that encounter.
Check moves and order before powering up
Two Pokémon of the same species can play very different roles with different moves. Read the fast and charged attacks on the recommended card, including any Elite TM notice. A recommendation that needs a move you cannot obtain is not ready to use just because the species is in your storage.
Against a shield-using opponent, reaching charged attacks quickly can matter more than one large damage number. Compare the available opening-swap and direct-lead settings: those assumptions affect which Pokémon takes damage first and when the model uses Rocket action delays. Follow the order the result describes rather than sorting your team by CP.
If a team loses one branch, inspect which opposing Pokémon causes the loss. A closer that covers that weakness can be more useful than replacing your strongest attacker with an even stronger version of the same role.
Make the recommendation fit your collection
- Set the counter options to exclude Shadows if you do not own usable Shadow attackers.
- Run the encounter and check the full recommended movesets.
- Use “I don’t have this” for unavailable recommendations, then read the replacement’s coverage and build requirements.
- Compare speed and survival with the same encounter settings so the change has a clear cause.
- Power up only after checking the final team’s moves, form, and missing coverage.
A replacement is a fresh recommendation, not a promise of identical performance. Keep an eye on the modeled losses after each exclusion. A result requiring several expensive builds may be less useful to you than a slightly slower team you can use immediately.
Use the first attempt to improve the next one
If the battle goes differently, record the opponent in each slot, your actual moves and levels, whether you opened with a swap, and the point where a Pokémon fainted. Those details distinguish missing coverage from a settings mismatch. Free storage space before starting so the catch encounter and rewards can proceed.
Keep the lineup reference and simulation assumptions together. An imported data timestamp tells you when a dataset was built; it does not prove that every live encounter has been observed since that time. Report a mismatch through the correction channel with the exact encounter details.
Sources and review notes
This guide combines the linked game documentation with the behavior and assumptions of Go Battle Forge’s tools. Examples are original illustrations. Game rules and available encounters can change.