The story of the game
James — I know this opponent's pawn-crawling drove you up the wall, so let's start with the verdict your annoyance was fishing for: yes, it's bad chess. Nine pawn moves in the first nine turns is objectively terrible, and your response was the textbook one — 4.d4, 5.e4, develop, 12.O-O. By move 25 the engine scored you at 91%. You won the argument about the opening. The game was lost somewhere else entirely: in a position you'd already decided was over, with two autopilot moves — 28.Rxc1 and 32.Qe3 — that each failed a scan you normally run. That's the real content of this loss. Annoyance doesn't blunder for you on move 10; it waits until move 28, when the opponent has been "beaten" and your attention has already left the board.
The key moments
15.Nb6! — remember how this win was built. No refutation hunt, no lunge. You developed, castled, took the centre, and the knight he chased to the rim on move 8 landed in the exact hole ...b4/...a5 created. 15...Rb8 16.Bf4 ran the rook down, 16...Rxb6 17.cxb6 won the exchange, 19.Bxg6+ took a pawn with check. This is the whole anti-crawl recipe: the punishment is a won middlegame, delivered by boring moves.
25.Nxd7 — don't cash the attackers (91% → 80%). Qg6 instead threatens the h6-bishop, and after 25...Nfe4 26.Qxh6 it's +5.7 with his king naked. Your e5-knight and queen were the attack; the d7-bishop was a spectator. Trade bystanders, keep attackers.
28.Rxc1?? — the recapture that wasn't forced (81% → 54%). Ask what the bishop on c1 was going to do — nothing. Bxe6! first: a pawn, a hit on d5, the d7-knight suddenly loose, and c1 still falls next move (+3.9). After the instant 28.Rxc1, black played 28...Qxd4 — centralizing with tempo — and his queen-plus-knights machine was back in business. You have the Qa4+ zwischenzug note in your English pocket already; this is the same idea from the other side. Recaptures are moves. They get the same scan as everything else.
32.Qe3?? — the queen was the glue (69% → 26%). The most instructive moment of the pair, because the idea was right and the order lost. Your f4-queen was doing two jobs: eyeing e5, and defending f7 down the file. Bxe6! first — the attacked bishop escapes with a pawn and tempo — and then Qe3+ next move trades queens into a winning ending. Same trade, one tempo later, totally different game. Played immediately: 32...Qxe3 33.Rxe3 Nxf7, piece gone, and the 2N + queenside pawns ending is lost for the rook. Before offering any trade: what is this piece currently defending?
Phase notes
- Opening: flawless by engine count — zero flags before move 25. Bottle this: vs system crawls you now have proof the boring recipe wins.
- Middlegame: the leak is specifically conversion moves — recaptures, trades, "cleanup." Those got a different, lazier mental process than your attacking moves. They need the same one.
- Endgame: after 33...Nxf7 the R-vs-2N ending was gone, but note how you kept creating problems until move 42 — that fighting habit is worth keeping even when it doesn't save the game.
Profile check
This game is your Mode-Locked Tunnel Vision master key wearing a new costume: the scan died the moment the game felt won. It also writes a new clause into "simplify when ahead" — simplify after the trade-safety check. And the relocated-pieces alarm now covers trades: re-read what a piece defends before you offer to remove it from the board.
What to drill next
- The winner's scan: next three winning positions you reach, run captures-checks-threats on every single move until resignation — especially recaptures. The scan you run at move 15 has to survive to move 35.
- Zwischenzug set: a week of in-between-move puzzles; you're missing them in one specific spot — before recaptures.
- Replay from move 27 against the engine as White. Find Bxe6 both times. Feel the difference between "the game is over" and "the game is over after I play accurately."