|
|
16. g4
|
In for a penny, in for a pound ... |

|
|
|
16... Bd6
|
The GK analysis lets Black do this without even hinting at any questionmarks... which might seem awfully odd considering that I can now fork his Knight and bishop simply by moving e5! But guess what? Those holes and weaknesses around my King - the consequence of stupidly letting him stay put in the center - they make the whole idea impossible! 17.e5? Nd5! 18.Qc2 Qh4+! 19.Kd1 Ne3+ and I might as well resign. |

|
|
|
17. d4
|
But now, surely I must be able to fork something! I have two (2!) potential forks going: e5 and d5. He cannot possibly escape them both ... |

|
|
|
17... Nd5
|
Right. Instead he can do this. And now 18.exd5 Bxd5 19.O-O-O Bxh1 20.d5 Qf6 (forced or mate on g7) 21.Qxf6 gxf6 22.dxc6 Bxc6 would mean playing against his pair of Bishops in a very open position - which would clearly favour him. |
2 comments
|
|
|
18. Qf3 Nf6
|
And now I stumble a bit. GK correctly flags this as an 'inaccuracy' and gives this, very instructive line as the alternative. It's probably not entirely correct (the GK analyses gets less precise towards their end), but the general idea is clear - and it shows again very clearly the consequences of having literally no protections in place around the King: here it let's Black get out of what would otherwise have been a hopeless bind. 19.Bg2 Na5 20.d5 Bd7 21.e5 Nxd5 22.Qxd5 Bc6 23.Qxa5 Bxg2 24.exd6 Bxh1 25.dxc7 Qh4+ 26.Kd1 Qxh3 |

|
|
|
19. d5
|
Aiming for a material bonus to offset my positional disadvantages. |

|
|
|
19... Nxe4 20. Qxe4
|
A general tip: do try to avoid placing the Queen on an open file with the King behind her and an enemy Rook in front ... Those things are bound to cause grief - which is precisely why Black chooses to let his Knight capture here rather than on, say, d5. |

|
|
|
20... Bb4
|
The bishop on e6 is untouchable, as 21.dxe6 Qxd2+ would make my position (even more) awful. And 21.axb4 is also firmly in no-go land after 21...Bxd5 22.Qc2 Bxh1 23.Qc3 f6 where I may have achieved material equality but is strategically lost. |

|
|
|
21. Qc2
|
This, on the other hand, is even worse ... considering how this ends, I really do think I should just have captured on b4 immediately. The reason I didn't: those three pawns on his queenside were just going to roll down and squash me then, considering that I haven't a shread of shielding in front of my King over there on the queenside. |

|
|
|
21... Bxd5 22. axb4
|
Finally deciding to sacrifice the rook in order to get the King away from that e-file. |

|
|
|
22... Bxh1 23. O-O-O Nxb4
|
Black is at +2 materially, and plus something innumerable strategically. GK evaluates his advantage to +2.75, but that is definitely too low. I could just as well have resigned here, as the total lack of (pawn) protection for my King, coupled with those open d- and e-files and the linked queenside phalanx of pawns, ensures Black an easy victory. |

|
|
|
24. Qc4 Nd3+ 25. Kc2 Nxb2
|
Neatly removes the most efficient piece remaining to me. |
2 comments
|
|
|
26. Kxb2 Bf3 27. Kc1
|
Both Knights were pinned. |

|
|
|
27... b5
|
Sacrifices a pawn to open the b-file. |

|
|
|
28. Qxb5
|
Capturing here is suicidal as the open b-file directly next to my exposed King means mating threats will now come quick and thick. But on the other hand, I cannot ignore the coming avalance either... |

|
|
|
28... Bxe2 29. Bxe2 Qf6 30. Qd3 Rxe2
|
The coup-de-grace, utterly isolating the King from my remaining pieces. |

|
|
|
31. Qxe2 Qc3+
|
A neat, very direct and totally deserving defeat. I violated several tenets in this game, and most importantly: I began operations against Black *before* ensuring the safety of my King. I will take pain to avoid doing so in the future! |
2 comments
|
|
|