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 2006-03-02 UTC
One point about this variant is the total strength of the array. The
simple
pieces have all the moves of the compound ones twice over. The key could
be
to think of the usual goal of capturing enemy pieces quicker than they
capture yours into gaining offensive advantage by capturing simple pieces
while preserving ones own compound ones and gaining defensive advantage
by
the reverse. The FIDE thought proces is often interms of exchanging
pieces
of the same type. The question here might be in terms of thinking in
terms
mainly of evaluating a compound piece against a number of simple ones
(typically three given the restraints to compounds?).
	All the same I can see that a subvariant in which compound pieces can
indeed cross the River in some limited way would be less divegent from
FIDE Chess and might go down well. A thought occurred to me to allow
crossing orthogonally forward and diagonally backward, or in the Gnu's
case Knightwise forward and Camelwise backward. Within each half of the
board they would be unrestricted, as would promotion on both end ranks. I
could envisage a similar subvariant of Anglis Qi itself, and also of
Alibaba Qi
(http://www.chessvariants.org/index/msdisplay.php?itemid=MSdualdirectionv),
an all-compound varaiant whose basic form allows crossing orthogonally or
Knightwise but not diagonally or Camelwise. Perhaps as all three vasic
variants end in Qi the subvariants should substitute some other Chinese
word conveying the divergent crossing. This might be better than the
other
alternative, prefixing with some attributive word resulting in long names
-
as well as being in keeping with the existing Anglis and Wildeurasian
indexing. Suggestions are welcome.

Edit Form

Comment on the page Wildeursaian Qi

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.