The Developer's Glossary.
Translating competitive TCG slang into actionable game logic. Map the state, execute the sequence, secure the checkmate.
Board State
The current snapshot of the game, including all Pokémon in play, discard piles, deck counts, and attached resources.
Developer Rule
Strategy Note
Treat the board as a persistent state object. Every action is a mutation that must be evaluated for legality and value.
Check-Step KO
Taking a knockout during the transition between turns (via Poison, Burn, or Adrenabrain). This is technically known as the "Checkup Step" in the official rules.
Developer Rule
Strategy Note
Forces the opponent to promote a target before your turn, enabling a multi-KO cycle and denying them "Coming into play" ability timing.
Checkmate
A board state where the opponent has zero legal cards remaining in their deck/hand that can change the outcome of the game.
Final Turn Checkmate
Developer Rule
Strategy Note
Count the opponent's remaining 'Outs' (Gusts, Disruption). If Outs == 0 and you have a path to take your remaining prizes, you have Checkmate. Execute the win condition immediately.
Fail Search
Playing a search card and intentionally finding zero targets to remove the card from hand without adding any cards to the hand. This is legal because the contents of the deck are not public knowledge.
Hand Compaction
Developer Rule
Strategy Note
Use for Hand Compaction to protect against hand-size-based disruption (e.g., Unfair Stamp or Iono) or to clear space for a "Draw until X" ability.
Liability
A Pokémon on the bench that is easy for the opponent to knock out for multiple prizes (usually an ex, V, or Rule Box Pokémon).
Iono Liability Check
Developer Rule
Strategy Note
If your prize map allows the opponent to win by only KOing Rule Box Pokémon, those are high-priority liabilities. Minimize their presence on the board unless they are providing essential logic.
Pivot
A Pokémon promoted temporarily to the Active Spot, often one with zero retreat cost, to allow the player time to evaluate the board before committing a resource.
Developer Rule
Strategy Note
Always have at least one free-retreat option (Pivot) available before promoting a non-essential target to the Active Spot.
Prize Mapping
The planned path to collecting all 6 Prize cards by identifying specific targets for knockouts based on their prize value (1, 2, or 3).
Winning Prize Path
Developer Rule
Strategy Note
Map your prizes based on turn efficiency (e.g., 2-2-2 or 3-3) rather than immediate opportunity. Always identify your opponent's "Winning Line" and disrupt it.
Sequencing
The specific order in which cards and abilities are played during a turn to maximize your odds of finding a specific resource. Professional players often thin their deck before using a "Draw" supporter to increase the density of "Outs" in the deck.
Optimal Draw Sequence
Developer Rule
Strategy Note
Always draw cards BEFORE playing cards that require discards, unless the discard is a prerequisite for the draw.
Slot Conflict
When multiple mechanics or items compete for a single limited resource slot, such as the Pokémon Tool slot or the Stadium slot.
Developer Rule
Strategy Note
Decouple dependencies by moving functions to non-conflicting slots (e.g., using an Ability for mobility instead of a Tool slot) to maximize the board's logical capacity.
Thinning
The act of removing low-value cards (e.g., Basic Energy) from the deck to increase the probability of drawing high-value logic or specific "Outs".
Signal-to-Noise Compression
Developer Rule
Strategy Note
If you have a way to move a card from the Deck array to the Board for free (e.g., Nest Ball for a redundant basic), do it immediately before any major draw action.
Uptrading
Forcing a prize exchange where you take more prizes than you give up (e.g., using a 1-prize attacker to knock out a 2-prize ex Pokémon).
Developer Rule
Strategy Note
Maximize HP or use damage reduction to move your attackers out of the opponent's "One-Shot" range, effectively forcing them to invest more resources into a single trade.