We won in rounds 7 & 8 by scores of 4:1 and 5:0, finished in second place, and promoted to the second league. Karol and I were the draws in round 7. The three contenders for promotion all won their matches by big margins despite opponents coming with more-or-less their normal teams.
My games turned out to not be that important for advancing, but they were very interesting. Round 7 featured another crazy double-hallucination, my third of the tournament and easily the worst of the three.
Round 7 game:
Round 8 game:
In round 7 I got my preparation, 6. c4 against the Kalashnikov:
I prepared 6. c4 specifically for this match, previously I had always played 6. N1c3. He knew it well. 6. c4 is actually quite interesting. Back in our day everyone played 6. .. Be7 here with the idea of a quick .. Bg5, but white has a cool move which completely foils that: 7. N5c3! Now 7. .. Bg5 loses to 8. Bxg5 Qxg5 9. Nb5! (better than 9. Qxd6 with some compensation), and 7. .. a6 is met with 8. Nd5 followed by 9. N1c3. No better is 7. .. Be6 8. Nd5 with further ideas of N1c3, Be3 and Bb6, since 8. .. Bxd5 9. cxd5 allows 10. Bb5+ due to the lack of .. a7-a6. Black can play 7. .. Nf6 but then .. Be7-g5 is off the table. It's funny that nobody figured this out 30 years ago, I guess N5c3 unprovoked instead of N1c3 is just too counterintuitive.
Nowadays people instead play this with .. g7-g6. My opponent had done that several times, using multiple move orders. It's what I focused on during my preparation, and it's what happened. There are a ton of transpositions so the important thing was to understand the plans. Position on move 10, black to move:
He played 10. .. Be6 here, which technically took me out of my preparation, but that's not that important, the bishop belongs on e6, the engine scores don't budge, and the plans are the same.
Move 17, black to move:
This is a normal kind of position. The engine always wants to leave the knight on d4, dance around it for a long time, leave the c-file uncontested (even if black doubles on it), and slowly play for f2-f4, with scores around +0.6 throughout. Black could just castle here, 18. Bxh6 is a double-edged sword. Instead he played the sharper 17. .. Qh4.
Move 19, white to move:
Here I started to go slightly wrong. I saw the best 19. f5 and thought that white would be better, but slightly overestimated my position after 19. fxe5. He actually mentioned after the game that he would have preferred 19. f5 here.
Move 21, white to move:
I played 21. Rac1, which is also slightly inaccurate. In general white does not contest the c-file in these positions. I knew that from looking at a ton of such positions with the engine yesterday, but here I decided that he had neglected the c-file enough that a change of plan was warranted. He understood the position well, and correctly exploited my move with 21. .. Rxc1, giving up the c-file and betting everything on .. f7-f5. This is of course the benefit of playing the same opening over and over, you know the ideas really well.
Move 23, white to move:
Best was 23. h3. I considered that, it was my top move at first, but in the end I concluded that I wanted my pawns on dark squares and king on a light square because my unmatched bishop was a light-squared bishop, so I played 23. g3 Kh8 24. Kg2. The logic makes sense but it walks head-first into 24. .. f5, which he played:
Here I went into the tank and used most of the rest of my time. I saw the best 25. Qd2 fxe4 26. Bxe4 Qg4 27. Qd3 but decided that black's initiative was too strong. There are ideas of 27. .. Ne2, 27. .. Nf3, 27. .. h5, even 27. .. Rf3. The move I most feared was 27. .. Nf3, which among other things ties white's rook to defending against .. Ne1+. I also didn't like losing the threat against h6, the variation feels "inefficient" for white. All of this can be defended though, the computer even says that white is a tiny bit better, and prefers 25. .. f4 with a small edge for black.
Instead I played 25. Bxd4 fxe4 26. Bxe4, sacrificing my queen. The resulting position seemed like it shouldn't be that hard to draw, although of course black has whatever chances there are. In theory this was probably the correct conclusion, although it's also easy to slip up, as I did. If I had understood that 25. Qd2 was only a little bit for black I would of course have played it.
Move 30, white to move:
This is the initial endgame. White has a grip on the light squares, and his d-pawn and bishop pair are strong. White also doesn't mind bishop trades since then black won't have a good piece to blockade the d-pawn with. We did trade those bishops. The double-blunder is coming.
Move 37, white to move:
My idea was to carve out a defended square for the bishop on f5, and stand pat with bishop on f5, rook on d3, and king moving around. The plan is fine, but I sleepwalked here with the immediate 37. Bf5??, allowing 37. .. e4+ with scores of -5. Even the resulting position doesn't look that trivial but I am sure the engine is right. Somehow he missed it too and a few moves later the draw was agreed. None of the spectators mentioned it either.
In round 8, I wasn't ready with the Gruenfeld yet, that's a project for the second league. I also was unable to prepare because the pairing was unexpected. We got another King's Indian. Position on move 11, white to move:
I looked at this position with Vasik during his final, and posted about it here. The main line is 11. Ng5, then 11. .. Nxg3 is unsound as we discussed. Instead he played one of the other moves, 11. Nh4. I couldn't remember if I should play 11. .. Nf6, 11. .. Nf4 or 11. .. Qe8 12. Be2 Nf6, went with the latter. The engine prefers the immediate 11. .. Nf6, after my 11. .. Qe8 the score climbs a little bit higher, to +0.7, but that's as high as it would get. From the point of view of engine scores this was easily my best King's Indian since I started playing again.
Move 13, black to move:
I had the thematic 13. .. f4 14. gxf4 exf4 15. Bd4 f3!! 16. Nxf3 Nb4 17. Qd2 Bf5 with a slight edge for black. I looked at this of course but didn't see 15. .. f3, which pulls the knight off f5.
Move 15, black to move:
I had a long think here, trying to decide between 15. .. Nd7 and 15. .. f4. It was basically a coin flip but I chose correctly (15. .. Nd7).
Move 18, black to move:
Another critical position. I played the obvious sacrifice, 18. .. Nc5, fairly quickly, and liked my position, but surprisingly, it's inaccurate. The computer scores 18. .. Nc5 as +0.0, which isn't shocking. What's surprising is how strong the simple 18. .. Bxd4 is, then 19. Rxd4 Nc5 20. Qd1 Qe7!, hitting the knight on h4, then if 21. Nf3 Bf5 and black has huge pressure. I underestimated this. A key motif in this position is the battle for the f5 square, which is of course the point of 11. Nh4.
Move 20, black to move:
Here I had another long think. I smelled blood but white's position is surprisingly resilient. I ended up settling for the slightly better endgame after 20. .. a4 21. Nxa4 Qxa4 22. Qxa4 Rxa4. This is actually black's best. Including 20. .. Bxg4 21. hxg4 a4 21. Nxa4 Qxa4 etc is equally good, white cleans up his pawns but loses Rg1.
Move 29, white to move:
This is the basic endgame, which I squeezed out. There were a lot of inaccuracies but no big blunders, and also no really critical decisions. We both played most of it with 2-3 minutes on the clock + 30 second increment.