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, Ralph Betza.

Enter Your Reply

The Comment You're Replying To
PBA wrote on 2002-03-29 UTC
John, I was going to reply to your, er, ah, <i>proposal</i>, but I find I can't think of <strong>anything</strong> appropriate to say . . . <p> <p> There seems to be Ruddigore in the air, since Ralph's submitted but as-yet-unpublished (I'm getting to it!) Chatter Chess also references it, not to mention the Ruthven (Negative Relay Knight) in 'Worse than Useless'. I wonder where I left my soundtrack CD? <p> <p> Balancing a Feebback and a non-Feebback army? One idea is to add all of th missing attacks from the back to the front: <p> <ul> <li> Kings are missing three back attacks, so they can capture (but not move without capturing) straight-forward or diagonally-forward two squares. </li><p><li> Queens are missing three attack lines back, so they can capture (but not move without capturing) in the forward four directions as Rhinos (four instead of three as it is symmetrical and because of duplicated squares). </li><p><li> Rooks only have a single attack line missing, so they get to capture (but not move without capturing) as a Halfling Bishop on the forward diagonals. </li><p><li> Bishops lose two attack lines, so they get to capture (but not move without capturing) narrowly forward as Rhinos. </li><p><li> Knights need four attack squares replaced, and they should be color changing, so they get to capture but not move without capturing as a forward or sideways Wazir. </li></ul> Would that balance it? <p> Another approach, but a very different game use a vertically cyclindrical board of 8x14, a line of Pawns on either side of the pieces, and have both armies consider forward the same direction. <p> PBA

Edit Form

Comment on the page Archoniclastic Chess

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.