King's Indian Attack — Win

Saturday, October 10, 2026 · vs H780A · View game on lichess ↗

A couple of these mistakes came from fast, almost reflexive moves — before playing a pawn push or a retreat, take an extra few seconds to check if there's a capture on the board first, like the one you missed on e4.

• ›Right before this, your opponent slipped with pawn to e4 instead of c4, handing you a real edge. Instead of cashing in with knight to f6 — which keeps developing and keeps the pressure on that awkward e4 pawn — you pushed to f4, locking the kingside shut and basically giving White time to regroup. Quick 6-second decision that gave back most of the advantage you'd just been handed.
• ›This one's a snap decision — 2 seconds, and you retreated the bishop to g6 instead of just taking on e4 with the d-pawn. That capture was sitting right there and wins real material and initiative. Worth training yourself to always scan for captures before playing a quiet move, especially when the position just opened up.
• ›Jumping the knight to d4 here looks active, but your king's still sitting in the center and this was exactly the moment to castle queenside and tuck it away. Leaving the king uncastled for one more move doesn't blow up immediately, but it's the kind of thing that turns into a real problem the second White finds a file or a diagonal to attack down.
• ›Your opponent had just castled short on the previous move — itself a mistake, since the engine wanted bishop to e4 instead — so the position was already leaning your way. Queen to h4 keeps some pressure, but pushing the pawn to h5 was the move that actually keeps the attack rolling forward with real threats against that king. Still good enough to win, just not the cleanest finish available.