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

Enter Your Reply

The Comment You're Replying To
Charles Gilman wrote on Thu, Nov 11, 2010 06:38 AM UTC:
'One hypothesis about why the Chancellor does so well is that the R has a weakness that is masked when N is added to form Chancellor. This weakness would be its relative slowness and difficulty of development, and perhaps its lack of forwardness (it has only one forwards direction).'

The fact that the Rook has just the one forward direction does not explain the lack of difference between Rook+Bishop and Rook+Knight as both wopuld gain from the non-Rook move. The more likely factors are (a) that adding the Knight move to a Rook with eight adjoining allies allows it to leap out of that space in a way that a Bishop move does not and (b) just adding the Rook move to a Bishop removes its colourbinding, adding it to a Knight rewmoves colourswitching, which is the Knight's property of always moving to the (not just an) other colour. Both compounds - and for that matter Bishop+Knight - can move to squares both of the same colour and of the opposite one. There are other kind of switching - the Silvergeneral is rankswitching (always moves an odd number of ranks), the Fibnif and Mushroom fileswitching (always move an odd number of files), and the Ferz and Camel both. Can everyone see why pieces that are both rankswitching and fileswitching are colourbound?


Edit Form

Comment on the page Ideal Values and Practical Values (part 3)

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.