The site has moved to a new server, and there are now some issues to fix. Please report anything needing fixing with a comment to the homepage.

The Chess Variant Pages

This page is written by the game's inventor, John Lewis.

Enter Your Reply

The Comment You're Replying To
Charles wrote on 2007-08-08 UTCPoor ★

This is not a problem: >>there are numerous positions in Chess960 where the King does not move at all if he Castles. >>

The original intent of castling was to move the king to either wing, centralize the rook and connect the 2 rooks.

It was ASSUMED that one of the wings was safer. This is not necessarily the case. Think of it as two bunkers located at opposite wings.

IN chess960, the king may already be in the wing bunker, but the rook alone needs to jump over to be centralized. Also if this wing is under attack the king can castle to the opposite wing.

So there is no issue if the king does not move at all.

The 'king moves two space' rule is for beginners who don't understand chess very well, and catering for them is ridiculous.

Castling in normal chess is only logical when visualized this way, not as a special 'king two space move' rule, which is what you are confusing castling to be.

For white a-side bunker is on your left with king on c1 R on d1 and h-side bunker on right with king on g1 and R on f1. In orthodox chess, this Castling move (to the bunker) can be made by moving king 2 spaces etc. But in Fischer Random, the moves are just different depending on the position.

Isn't that quite logical. If I as King am already in the bunker or quite close, I don't have to move very far, but my rook has to move over to center. Note, that it is assumed in Chess that the bunkers are in the wings. Otherwise, why can't the king just jump anywhere where it may be 'safe'?

Fischer was no dummy when he invented this variant. The castling rule is what makes this Fischer Random variant unique.

Otherwise you have shuffle chess and NO CASTLING!

Edit Form

Comment on the page Castling in Chess 960

Quick Markdown Guide

By default, new comments may be entered as Markdown, simple markup syntax designed to be readable and not look like markup. Comments stored as Markdown will be converted to HTML by Parsedown before displaying them. This follows the Github Flavored Markdown Spec with support for Markdown Extra. For a good overview of Markdown in general, check out the Markdown Guide. Here is a quick comparison of some commonly used Markdown with the rendered result:

Top level header: <H1>

Block quote

Second paragraph in block quote

First Paragraph of response. Italics, bold, and bold italics.

Second Paragraph after blank line. Here is some HTML code mixed in with the Markdown, and here is the same <U>HTML code</U> enclosed by backticks.

Secondary Header: <H2>

  • Unordered list item
  • Second unordered list item
  • New unordered list
    • Nested list item

Third Level header <H3>

  1. An ordered list item.
  2. A second ordered list item with the same number.
  3. A third ordered list item.
Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.

Alt text for a graphic image

A definition list
A list of terms, each with one or more definitions following it.
An HTML construct using the tags <DL>, <DT> and <DD>.
A term
Its definition after a colon.
A second definition.
A third definition.
Another term following a blank line
The definition of that term.