Your network blocks the Lichess assets!

lichess.org
Donate

Screenshot by kringleman5566

Bishop and Rook Sacrifice for the Win

ChessAnalysisTactics
Two sacrifices back to back

Hello readers and happy international chess day. I have not been playing chess for the past year. As motivation to keep me playing, I decided to make this blog post and hopefully more. I used to blog on my old Lichess account, but I deleted that account a while ago. However, I still have their chess.com equivalents. Below is the full game and links to older blog posts.

https://lichess.org/WYqzJUtp/white#0

https://www.chess.com/blog/TheSponge8000/my-best-draw-ever-mce-part-2
https://www.chess.com/blog/TheSponge8000/my-chess-experience-part-1-first-blog-ever

Initial Thoughts

At the time, I had been playing some bullet games, but my quicker reflexes weren't there, and I was losing quite a lot. Blitz seemed like a better alternative, so I gave that a whirl. Honestly, this game was fairly banal until the sacrifices. It has your typical d4 and e4 paw duo, minor piece trades, doubled f pawns, etc. Although, what Lichess considers mistakes seem like such ordinary developing moves that it's somewhat startling. Before I continue, I want to say that my opponent played a very good game, and I hope they have more good games in the future.

Opening Analysis

I had the white pieces and I'm a d4 player. My opponent went for fast queen bishop development, which in my experience, is often hindered by d4 openings, so I can't say that I blame them. I pushed my pawns to make a strong e5 and d4 chain while developing my minor pieces. My opponent chose instead to develop their minor pieces first before committing pawns to the center. Usually, this works just fine and I've done this myself; it's a very dynamic style of play, and I don't think that was the issue here. In the position below, they've pinned my queen knight and have placed their own knight on e4. This is such a common occurrence for me in d4 games that Bd2 comes almost as second nature. It unpins the knight, thus letting it attack their e4 knight and almost forcing a trade (d5 or f5 defend could counter that idea). The engine wants me to kingside castle, but I was hesitant because of their light-squared bishop.

https://lichess.org/WYqzJUtp/white#12

Middlegame Analysis

They traded their central knight for my bad, dark-squared bishop, but this allowed them to take my f3 knight and double my f pawns. This effectively prevented me from kingside castling. To better prepare for the eventual queenside castle, I thought kicking their bishop with a3 would be a decent idea. Apparently, the engine considers their Be7 move to be a mistake. Maybe taking my queenside knight would weaken white's defenses for the future? Also, it would force the queen to retake, causing it to no longer eye the important h6 square. My queenside castle was also flagged as an inaccuracy, preferring an immediate Rg1. I could have had a pinned pawn on f4 with Bg5 (only f4 saves the queen). The engine deemed black's 11th and 12th moves as a blunder and mistake, respectively. This is probably due to the fact that they both ignore the rook's g file threat. However, they seem like such no-brainer developing moves that it reminds me that you cannot take anything for granted in chess. The engine wants white to rook sacrifice by taking on g7; which forces a black to lose their queen (Kxg7, Rg1+ Kh8, Qh6 Bg5+, Rxg5 Qxg5+, Qxg5). Unfortunately, I did not see this. I instead immediately went for Qh6, which prompted g6 and created the position below:

https://lichess.org/WYqzJUtp/white#26

I spent about 90 seconds considering my options, which is a lot for blitz. This is the key position in the game, but it's not too uncommon for the rook and queen to be coordinated like this on the g file. I knew that some attack could be made but wasn't exactly sure what it would look like. Only now did I consider sacrificing the rook. I needed assurance that the attack would be more fruitful before giving up such a powerful piece. That's when I realized that Bxg6 threatened checkmate, forcing them to capture with a pawn. After that the rook can take, then the queen the third pawn and the king is completely exposed. Although, after Rxg6+, the engine says black should go to f7 then e8, but this leaves and extra rook in the game for white and the e6 pawn exposed, so I don't think most human players would do this. After both sacrifices, I played Qh5+, which is different from Qh6+ since it still covers the f7 square, leaving no breathing room for the black king. With Rg1+, the king has nowhere to go, forcing Bg5+ then Qxg5+. I love how the recapturing check helps me in this case since it's virtually impossible to miss-click the retake. But after black lost their queen, it was essentially game over. With a knight fork at the end came the resignation.

Conclusion

I wish I could play chess this good each time. I'm glad I could find the winning combo under time pressure (there's a reason my bullet rating is so low). Unfortunately, I don't think I'll see these sorts of combos each time I play, either due to position or misjudgment. One tiny difference, like black playing g3 earlier and then playing Kh8 and letting their rook go to g8, would have made this game impossible. I probably would have also played Nc6 or d5 if I was playing black this game. The white side does have a fairly decent advantage at choosing an opening that they are comfortable with each time. For me, there is something much superior about d4 than e4. Maybe I'm just more positional? Either way, this was a fun game regardless.