BASIC — Hook: You're staring at the lead and don't know who moves first
You bring the team you've spent dozens of hours on into a Ranked Battles lobby. Team Preview flashes by, you tap an attack turn one — and the opponent, one Speed point faster, takes your core before you blink. You never get the tempo back.
First instinct: "Did I do something wrong?" No. What this lesson sharpens is the invisible decision you made in those first five seconds: who moves first, what the opponent wants, what your tap is actually betting on. Story mode never forced that decision, so of course you can't make it yet. That's expected — not a failure.
BASIC — Core: Opposite goals, so losing is the normal output
Story mode is built to let you win. Ranked Battles is built to find your weaknesses. Opposite goals → opposite results.
Story mode never asks you to spend Stat Points (66 total, cap 32 per stat, IVs locked at 31, Level 50). It never asks you to predict the opponent's move. It never gives you a Team Preview cut. You've practiced none of these three skills.
The minimum correct model is one sentence: your job each game isn't to win — it's to extract exactly one "I can use this next time" conclusion. Wins are an outcome; conclusions are an asset. Tonight you only bank assets.
INTERMEDIATE — Worked → Faded: take one loss apart into numbers
Full worked example. Say you lead Garchomp in singles into the opponent's Dragapult, and you reflexively tap an attack.
Run the speed line first. At Level 50, IVs locked 31, positive nature, Stat Points fully into Speed: Dragapult has base Speed 142 — the fastest in this roster; Garchomp has base 102. The gap is too wide for any allocation to flip — the opponent goes first 100% of the time. So the attack you tapped is happening under the condition "can I survive their hit first," not "can I move first and snipe theirs."
Now the damage dice. Champions rolls 85%–100% across 16 equiprobable steps, so a KO is never yes/no — it's a probability. Suppose their hit on your Garchomp reads "12/16 to KO." That means 12 times out of 16 you're just gone, 4 times you cling on. By tapping blind, you signed up for a 75%-to-lose-a-mon gamble you didn't even know you were making.
The one conclusion you extract: "Check the speed line before deciding whether to attack or feel it out with Protect." One. That's enough.
Your turn (faded). Next game, don't tap immediately. Ask three things: (1) Between my lead and theirs, who has higher base Speed? (2) If I'm slower, what's their hit's KO probability on me, roughly out of 16? (3) Since I'm slow, do I switch, Protect, or bet they won't hit me? Can't answer (2)? Fine — that gap is tonight's conclusion.
INTERMEDIATE — When / Decision: when to run the autopsy
Keep this as an if-then:
- If you lost and have no idea where it broke, then replay the one turn where "I thought I was safe and wasn't." The conclusion is buried there.
- If you lost knowing exactly why (you forced a mon in that hard-counters you), then the conclusion is a teambuilding one — log it for next time.
- If you won but it felt handed to you, then still extract one — "why did they hand it to me" is worth more than "why did I win."
Pull only one per game. More than that and you won't remember, won't train it.
INTERMEDIATE / ADVANCED — Exceptions: when this rule lies to you
"One thing per game" isn't a blind ritual. Three exceptions:
- A losing streak isn't a learning streak. If five games running produce the same conclusion ("missed the speed line again"), it's no longer new data — stop, drill that specific thing, instead of grinding more games to feel productive.
- Variance games produce nothing. Their Fire Blast is 85% accurate and you only won because it missed three times — there's no reusable lesson here. The Ranked Battles dice (16 damage steps, Paralysis now only 12.5% full-stop, Sleep ≤3 turns) carry built-in variance; don't mistake luck for insight.
- A build hole isn't a play conclusion. If your team runs two mons sharing a weakness (say double Ice-weak), that's not "the one thing I learned this game" — it's a hole you should have plugged at teambuild, and in-battle play can't refund it.
INTERMEDIATE / ADVANCED — Mistake-Autopsy: the classic beginner error, and the fix
The mistake: using "did I win this game" as your only feedback signal. Win → team's fine. Lose → swap a Pokémon.
Why it's wrong: single-game variance is enormous — the 16-step damage dice, accuracy, whether the opponent misplays, all baked in. Tuning your play off a high-variance signal is chasing signal inside noise; the more you chase, the more lost you get. The textbook symptom: "lost three, instantly rip the team apart." You end up forever rebuilding and never actually training the same read twice.
The fix: switch the feedback signal from "win/loss" to "was my key read this game correct?" Read was right, you lost (they got lucky)? Don't touch it. Read was wrong, you won (you got lucky)? Log it and fix it anyway. You're tuning read quality, not win rate — the win rate follows on its own.
INTERMEDIATE — Predict-then-Reveal: guess before you peek
Scenario: Singles. Your Garchomp (max Speed) faces the opponent's Hydreigon. You want to tap Earthquake. The FIRST question in your head at the lead should be which of these?
A. "Does Earthquake KO it in one?" B. "Who moves first — and if I'm second, what's their hit's KO probability on me out of 16?"
Pick before reading on.
Answer: B. A is story-mode thinking — it only computes "me hitting them." B is ranked thinking — lock the turn order first, then ask whether your attack even holds up given they move first. Garchomp at base 102 vs Hydreigon at base 98 is a four-point speed line — if they run a positive Speed nature and you don't, they go first. That's exactly the variable A never sees and B nails immediately. Order first; only then does damage probability mean anything.
ADVANCED — Now-Do-This: run a real loss autopsy with the AI Coach
Open the AI Coach and do not ask "what team should I use" — that outsources the learning. Do this specific thing instead:
- Pick a game you actually lost today and tell the Coach both leads.
- Have it compute the speed line for those two: who's faster by base, can allocation flip it, and in the worst case are you first or second.
- Tell it the move you actually tapped that turn and ask: "Given they moved first, did my play hold up? If not, should I have used Protect, switched, or bet?"
- Take the one conclusion the Coach gives you, write it in your own words as a single line, and save it to your notes. One per game. Bank ten and you're no longer the player who tapped attack blind.
You're not behind. You just haven't started banking data systematically yet — start with tonight's loss.