Check out Symmetric Chess, our featured variant for March, 2024.

Enter Your Reply

The Comment You're Replying To
Charles Gilman wrote on Wed, Feb 22, 2012 06:45 AM UTC:
Since I first put this variant in the list of ones that I might overwrite, I've been wondering how I might salvage it. It is my only variant with a specifically Welsh element, in contrast to many variants of mine featuring the Unicorn associated with Scotland, in either its cubic or its hex form. I feel that I have still not fixed the imbalance of different number of pieces able to make trhe crossing without a Ferry and would do better to have the same number of such pieces on each side. Five aside seems better than three aside, so I wondered about having Rooks on both sides and adding Queenfilers (Queens restricted to moves that change file) to the Welsh side. This would give both players the same number of linemoves spread between their pieces, though leaving the remaining advantage for the Welsh side (the second player, after all) as regards short-range moves and not having any of their pieces colourbound. It would also mean that I could lift the restriction on non-dragons crossing and capturing in one move. I was already thinking along these lines, but the recent debate on what constitutes Chess made me realise what a constant the Rook has been.
	However, what board would suit these extra pieces? I can see that things will get a bit cramped on an 8x8 board, and I do not particularly want to get rid of any pieces. The Knight is not quite as much of a constant worldwide but it does go well with dragons thematically. A larger army would mean abandoning the 'standard equipment' tag anyway. My instinct is to add two ranks, to have a squarer block in each half of the board than addig two files would offer and lengthen possible Bishop moves from three steps to four. Two lots of five ranks would also echo Xiang Qi. Does this sound a good way of proceeding?

Edit Form

Comment on the page Flight and Ferry

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.