Question to chess gurus: What would be your strategy against chess player who queen trades all the time?

Question

Question to chess gurus: What would be your strategy against chess player who queen trades all the time?

Answer 1

Avoid exchanging Queens if at all possible.  That person obviously is comfortable playing without either side having a Queen, so you need to take them out of their comfort zone.

If the exchange of Queens is often forced (i.e. their Queen attacks your King from close range and the only way out of it for you would be to exchange Queens), then castle early. This will separate your King and Queen and make it more difficult to attack both with their Queen.  Just make sure your King is adequately defended in the castled position.

It's always good to avoid favorite positions of  your opponent whenever possible.

Good Luck to you

(and yes, the Capa book is excellent)

Answer 2

Look at the bigger picture.  Someone who trades queens all of the time is actually more comfortable in the endgame.  This may mean that he or she is afraid of complex openings and/or the middle game.  Your strategy, which in chess terms also includes the preparation that you make before you even start playing, should revolve around learning your openings deeper than your opponent.  What does your opponent play more often 1e4 or 1d4? Learn which ever one your opponent is least comfortable with.  Also remember a time honored tactic: when down pieces, trade pawns and vice versa. Hope this helps.

Answer 3

Learn to play the End Game.

The best way is to study "Chess Fundamentals" by Don Jose Capablanca.  In the first couple of chapters he shows how to play without a queen.

Answer 4

Get good at end games.:)

Seriously, you can't stop it.  Just be better at his game.

Answer 5

There are a multitude of answers.. but overall the game is won by position NOT strength.. so I'd say to work on employing a strategy in which you "sacrifice" the Queen for positional dominance.

You can also learn to play XiangQi.. and then you'll have removed the problem. :)