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

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Wed, Jul 19, 2006 04:10 PM UTC:
I hope to stem the misuse of the term rider before it continues. Rider is a technical term in the field of Chess variants for a piece that may make multiple leaps in the same direction and of the same distance, so long as every space it passes over is empty until it reaches its destination, which may be empty or occupied. In Chess, the Rook is a Wazir-rider, the Bishop is a Ferzrider, and the Queen is a Kingrider. Rider is not synonymous with Nightrider. This piece is so called because it is a rider of Knight leaps, a Knightrider. The K is dropped because Nightrider is already an English word that's suitable for a Chess piece. The name of Cannonrider is confusing, because first the Cannon is already a rider, at least insofar as it can move like a Rook when it's not capturing, and when it captures, it moves as a hopper, not as a simple leaper. Each rider piece is normally related to an analogous leaper, not a hopper. But I could imagine extending the use of rider to cover a piece that can make multiple moves of the same type in the same direction. For example, I could imagine a Cannonrider to be a piece that can make multiple Cannon captures on the same move, so long as there are enough screens, empty spaces, and pieces in the same line. I'm not recommending this extension of the term, but it at least seems more natural than using the term rider to refer to a specific kind of rider.

Edit Form

Comment on the page Cannonrider 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.