Scotch Game — Loss

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

Twice in this same game the engine wanted that knight hopping to b5 and you skipped it both times for a developing move instead — when a piece of yours is attacked, scan for a retreat that also creates a threat before defaulting to 'just develop something else.'

• ›Here's the moment — your knight on d4 is attacked by the queen on f6, and knight to c3 does nothing to defend it. The engine wanted knight to b5, keeping the piece active and swinging at c7 instead of leaving it as a free lunch. You got away with it only because they missed queen takes on d4 next move — lucky break, not a save.
• ›Same song, different verse — the engine is asking for knight to b5 again, and instead you grabbed the knight on c6. Trading it off here gives up the initiative you should've kept with the knight hopping into their position, and it's the second time in two moves you passed on that same idea. Worth noticing the pattern, not just the single move.
• ›This is the big one — bishop to f4 instead of the tucked-in bishop to f2, and the eval just falls off a cliff. The safer square keeps the bishop protected and out of harm's way; putting it on f4 exposes it and basically hands the position back to your opponent after a game where you'd actually been doing fine.
• ›Pawn to h3 here is a bit of a luxury move — it took you 17 seconds and doesn't actually address what's going on. Rook to f1 was the move, getting a piece into the game instead of spending a tempo on a pawn push, and that gap in activity is part of why they kept clawing back in.