Castle question

I am black. Shouldn't I be able to castle Queen side here? Queen side pieces as well as the Queen are out of the way.

Hi, after you move your c8 bishop and d8 knight, you should be able to castle king side or queen side

You have to move all of the minor pieces before ya can castle? That don't seem right.

Look at the way the castling movement worked in that case. The bishop on c8 was blocking the castle. I don't play 960 so I'm not particularly familiar with the rules, but that's my thought.

I thought that for castle purposes you assume the King is on it's normal square. That's how it's always worked before.

I like 960 because it does away with all the memorized openings etc. giving us beginners a fighting chance. Levels the playing field a bit. but there has to be consistancy in the rules.

1828, exactly, and the bishop on c1 was preventing the king from going to its "normal square" on c1.

960 is similar to reg chess in the castling rules. In reg chess no piece can be between the King and the castling Rook. In your case you still have 2 pieces in between your King and King side Rook. Now castling Queen side in this position you have no pieces between your King and Queen side Rook but you have to move the Bishop on c8 and the Knight on d8 in order to castle Queen side. The Rook after you castle Queen side would be on d8 and the King would be on c8 there can not be any pieces on the squares the King and Rook will sit on after you castle. Always remember that the Queen side and King side castling go by where the King and Queen would be in a normal game. Queen always on her own color. Cheers

I'm on my second Chess960 game and even the playback has problems with showing a castle when you back, then forward through the move. You have to hit the (in this case) 0-0-0 to initiate the final castle. No big deal.

@ dWF5Gt: Yes it is a bug in the chess.com software. All 960 games have a problem in the analyze board and the main game going backward and then forward were the Castling move happens. They are coming up with a new site release soon so I doubt there is anybody working on that bug :)