♟ Superbet Classic 2025 — Round 6 in progress ♞ New opening theory article: King's Indian Defense deep dive ♜ Puzzle of the Day: White to move — find the win ♝ Training Tip: Study endgames for 10 minutes every session ♛ Events Recap: Magnus wins Norway Chess blitz ♚ New to chess? Start with our Beginner's Training series ♟ Superbet Classic 2025 — Round 6 in progress ♞ New opening theory article: King's Indian Defense deep dive ♜ Puzzle of the Day: White to move — find the win ♝ Training Tip: Study endgames for 10 minutes every session ♛ Events Recap: Magnus wins Norway Chess blitz ♚ New to chess? Start with our Beginner's Training series
Home Puzzles The Decoy Sacrifice: Trading Queens to Win a Piece
Puzzles

The Decoy Sacrifice: Trading Queens to Win a Piece

Pawn Storm Staff June 4, 2026 at 8:23 AM 5 min read

A queen sacrifice that isn't really a sacrifice at all. We'll dissect a clean middlegame combination where giving up the lady forces a winning knight fork. Then we'll drill the underlying decoy-and-fork pattern with supporting examples.

Solve the Puzzle

When the Queen Is Just Bait

With Magnus Carlsen tearing through rapid events this month, I keep seeing the same thing from his games that I want club players to internalize: strong players don't count material first. They count coordination first. A queen sacrifice looks scary on the surface, but if the move that follows it wins a whole piece by force, then it was never a sacrifice — it was an investment with a guaranteed return.

Today's centerpiece is a gorgeous little middlegame combination that runs on exactly this logic. Set up the board:

FEN: 2r2rk1/6pp/1q6/ppNb4/3PpQ2/P1R4P/6P1/5RK1, White to move.

Reading the Position

Let's take stock before we calculate. White has a knight superbly posted on c5, a rook on c3, and a queen on f4 eyeing the dark squares. Black's pieces look active — rooks on c8 and f8, a bishop on d5, queen on b6 — but notice something crucial: Black's back rank is loose. The king sits on g8 with only pawns on g7 and h7 for company, and the rooks on c8 and f8 are the only defenders of the eighth rank.

That f8-rook is the key character. It's defended once — by the king. The c8-rook is defended once — by the f8-rook. This is a classic overloaded-and-undefended back rank waiting to be exploited. The question is how to crash through.

The Combination

Here's the full sequence. Don't peek ahead — try to see why each move is forced.

  1. 1. Qxf8+!! White hurls the queen into f8. Black must recapture, and the only legal recapture is...
  2. 1... Rxf8 The c8-rook is now the lone defender it just became — wait, look again: the c8-rook captured. Now the back rank has changed.
  3. 2. Rxf8+ White's other rook takes on f8 with check, and the king is forced to grab it.
  4. 2... Kxf8 Now the dust settles. Material count: White gave up a queen and got back a rook and a rook — so it's queen for two rooks, roughly even. But this was never about the material exchange. It was about geometry.
  5. 3. Nxd7+! There it is. The knight on c5 leaps to d7 with check. It forks the king on f8 and the queen on b6!
  6. 3... Ke7 The king steps off the fork, attacking the knight.
  7. 4. Nxb6 White scoops the queen. The knight escapes with check having done its job.

Tally the whole operation: White invested a queen, collected two rooks AND the black queen via the fork. Net result — White emerges with a knight (and the bishop on d5 hanging next) for nothing. A completely winning position from what looked like an even middlegame.

Why It Works: The Decoy

The engine label here is "decoy," and it's one of the most important tactical ideas you can own. The combination works because of a forcing chain: every Black reply was the only legal move. Qxf8+ and Rxf8+ existed purely to drag the black king onto f8, where it would sit on the same knight-fork diagonal as the queen on b6.

The d7-square was the magic intersection: a knight on d7 hits both f8 and b6. White's entire job was to force a piece onto f8. The queen and rook were the delivery trucks.

Drill the Pattern

Two supporting ideas to lock this in:

Pattern 1: The fork square exists before the sacrifice

Always ask: "If I could teleport my knight to a checking square, what else would it hit?" Here, a knight on d7 forks f8 and b6. Once you spot the latent fork, you reverse-engineer the forcing moves to set it up.

Pattern 2: Loose pieces drop off

Black's queen on b6 was undefended and sitting a knight's-move from the king's escape square. As GM John Nunn says, "Loose Pieces Drop Off" — LPDO. If Black's queen had been on, say, a6 instead of b6, Nxd7+ would fork nothing and the whole combination evaporates. The undefended queen was the vulnerability that made everything click.

Takeaway

Before you reject a queen sacrifice, count the return trip, not just the departure. Look for the intersection square where a knight check creates a fork, then ask whether a forcing sequence can plant an enemy piece on the right square. Material isn't sacrificed when it comes straight back with interest. Train your eye to see the fork first and the sacrifice second — that's the order Magnus calculates in, and it's the order that wins games.

tactics decoy knight fork