Check out Alice Chess, our featured variant for June, 2024.

Enter Your Reply

The Comment You're Replying To
Charles Gilman wrote on Mon, Aug 1, 2011 06:01 AM UTC:
First question, given that Kings can cross over if they can get to a Ferry need I still consider the options of Bare King, Bare Facing. and Win by Stalemate or should I dismiss them?
	I can see the problem of a King in particular being safe from so many pieces while on a Ferry, and the imbalance in pieces that can cross without a Ferry being too strong to counter even the first move and the imbalance in dragons combined. Incidentally I now notice that a Silvergeneral would be as unsuited to this game's rules as to its theme - once having crossed, it could not cross back.
	Here are 9 alternatives for strengthening the Golddragon and Copperdragon, in the order that I thought of them. All are intended in addition to the ability to make a normal capturing move - but never capture two pieces in the same move.
1 They can share a cell with a Ferry but not take one with them.
2 They alone can capture/check any one piece en route to an empty square.
3 They alone can capture/check one piece on a Ferry en route to an empty square.
4 They alone can capture/check any one piece beyond the end of a move to an empty square.
5 They alone can capture/check one piece on a Ferry beyond the end of a move to an empty square.
6 They alone can move to a square with a Ferry on (but not of course an ally) and immediately move the Ferry away.
7 All pieces can move to a square with a Ferry on (but not of course an ally) and immediately move the Ferry away.
8 Both 2 and 4.
9 Both 3 and 5.
	Each would apply to equal numbers of both players' pieces. 1 Would play havoc with the notation, as I was trying to make a virtue out of reprsenting them with GD and CD when G and C usually mean other things, including the much weaker Goldgeneral and Coppergeneral respectively. 2 and 3 would fit with the names (picking something off with their huge talons) but they could still not capture or check an enemy on a Ferry on an end file from another file. This would reduce the Gold v Copper advantage. 4 and 5 could also be seen to fit the names (breathing fire on the piece) but are a little far-fetched, and they couldn't capture or check an adjacent enemy. 6 would not be such a good match for their names. 7 would address that oddity and speed things up but be a big departure from previous Ferry use. 8 and 9 would address the shortcomings of their respective components. My instinct is to go with 9 as the minimum added power to allow them to capture pieces on Ferries anywhere.
	I've spotted another gap in my rules. Can a piece on a Ferry capture a Golddragon or Copperdragon? I can see an argument both ways. Certainly barring it would be in accord with the current rules, but I think that it should be allowed once I have settled on a change. Dragons should after all be vulnerable to someone on a Ferry drawing up alongside them.

Edit Form

Comment on the page Flight and Ferry

Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
Avoid Inflammatory Comments
If you are feeling anger, keep it to yourself until you calm down. Avoid insulting, blaming, or attacking someone you are angry with. Focus criticisms on ideas rather than people, and understand that criticisms of your ideas are not personal attacks and do not justify an inflammatory response.
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.