Check out Grant Acedrex, our featured variant for April, 2024.

Enter Your Reply

The Comment You're Replying To
Charles Daniel wrote on Wed, Jul 16, 2008 05:24 PM UTC:Good ★★★★
Actually, this is a dramatic improvement to the original castling rules. From a defensive point, yes it is best to move the king to the corner where it can protect its pawns.

One can place the rook in an attacking position in the appropriate file - so it is not just a defensive move but an offensive one. Rather than make two moves and then move the rook to the center file. With one step castling one can move the rook to the center right away.

The castling rules in my games e.g. Birds and Ninjas are a bit different. The rook must end up next to the king. Thus, to bring the rook to the center file, the king should move one step. Also, it is permitted to check the opposing king with castling. (but not to castle out of check) This is the way it is in std chess and I see no reason to change this as the rules here state.
For my version which I call 'Flexible Castling' you just remember to move the king 1-x amount of steps towards the rook and move the rook over next to the king. One confusing position is when I permit the king to occupy the rook square and the rook moves 1 square over. This is the most defensive castling position - allowing the king to protect wing pawn.
Castling is best understood as a joint maneuver to connect the rooks, centralize the rooks and to tuck the king away in the corner. Sometimes it may be necessary to centralize the rooks and start a series of offensive moves .
Flexible castling is perhaps a bit simpler though a bit more complicated than the regular castling rules. The increased strategical/tactical possibilities more than make up for rule complexity.

Edit Form

Comment on the page Free Castling Rule

Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
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.