The Chess Variant Pages



This page is written by the game's inventor, Charles Gilman.

Enter Your Reply

The Comment You're Replying To
Charles Gilman wrote on 2009-01-15 UTC
This is an interesting theory, but details of how the pieces were chosen belie it. Certainly part of the motivation was an exercise in choosing pieces subject to a not uncommon restriction, but I would hope the game more playable than one where each letter's piece were indeed chosen randomly.
	The criteria in the introduction rule out most combinations fitting the broader Duke criteria. Using 'as many FIDE piece types as practicable' restricts B, K, P, Q, and R to the FIDE pieces, while 'grouping piece types as much as possible with relatively few one-offs' also rules out vast numbers of combinations. Insisting on 'pieces representable by 4 distinguishable FIDE sets on 4 FIDE boards' rules out too many weak pieces, as pieces of which there are only 1 or 2 should be able to hold their own on a large board. Thus I have chosen to have 8 each of the 4 piece types least suited to being present in small numbers.
	All the same, any comment giving new ideas is welcome. I have been inspired to review my choice of pieces in light of additions to the pool since this idea first came to me, and replaced the Hood, which is really too short-range for a lone piece on a large board, with the long-range Harrower. One of the suggestions for A, Antelope, might be an improvement on Ambrose, both thematically and perhaps in terms of understandability. Coincidentally the Antelope has a subset of the Ambrose destinations but on an unblockable path - like the Nightrider relative to the Rhino. I am deferring highlighting the page as changed until I have decided whether to make that change as well.

Edit Form

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

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.