The Chess Variant Pages

Enter Your Reply

The Comment You're Replying To
George Duke wrote on 2007-08-28 UTC
Here are several hundred more from an earlier generation's try (1998 article) for recent threads 'Multiform' and 'FatallyFlawed' and also 'Complementarity' and 'ShortRange Project'. Figure about half these would ShortRange-qualify, and when we called it 'The Deranged Project' to JGood last year, hey were just kidding, because in fact are, and further intending to contribute. With our tentative best alternative to RN and BN as (R,Mao) and (B,Moa) instead, seriously thinking they are superior, we need the right evaluative criteria. Recently some have used the old cliche, 'Have you played it?' That was popular around 2001 or 2002, and had died out after Michael Howe averred that a trained observer can tell how a game plays just perusing the Rules. Case closed, tacit agreement came because, of course, it is impossible to do justice playing 10,000 different Chesses. My corroborating Comment in 2004 was that a good game surely warrants 10 days(hour a day), and multiply 10 days by 4000 CVs, and that 40,000 days have been reached by only maybe 1,000-10,000 out of the total 100 billion humans that ever lived. So, realistically, who can conceivably keep up? This List does not define all its pieces but they can be found. In a random sample, letter K, letter T, we know about half of them right away and where to go for about half more, so 'List of Fairy Pieces' 75% comprehensible. Which are only fanciful? Or are some more important than others? It seems incumbent to develop systematic judging by principles other than playing. Excuse this Comment's mixing together in the general idea mere pieces and actual full-fledged CVs, there being some rough comparability if only in the utter lack of limit to inventiveness. [Also, later noticing that Truelove's own Comment says all pieces in this particular list are from DP's 1994 ECV]

Edit Form

Comment on the page List of fairy pieces

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.