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

Enter Your Reply

The Comment You're Replying To
Thomas Alsop wrote on Thu, Jan 6, 2005 12:53 PM UTC:Good ★★★★
Before I was aware of the existence of Capablanca Random Chess(CRC), I had
designed my own hybrid of Fischer Random Chess(FRC)(sometimes known as
Chess960) and Capablanca Chess. My hybrid, Capablanca84000, includes 84000
set-ups as opposed to the 21259 for CRC.
The rule differences are:
1. CRC states that the queen and archbishop must be placed on opposite
coloured squares. Since neither piece is colour-bound (unlike the bishops)
I had not chosen to include this rule. Indeed, a common and logical first
move for the archbishop is that of the knight-style jump, thus landing it
on a different coloured square. If it can be proven that the jump is the
more common first move for the archbishop, it would be equally logical to
place the queen and archbishop on same coloured squares.
2. CRC states that each pawn must be covered. FRC does not and neither
does Capablanca84000. If FRC did include this rule, it would no longer
contain 960 set-ups since some contain uncovered pawns. For example,
set-ups which begin with knight-knight-rook starting from either the a- or
h-file contain 2 uncovered pawns on either the a and b files or g and h
files.

Edit Form

Comment on the page Capablanca's chess

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.