Check out Glinski's Hexagonal Chess, our featured variant for May, 2024.

Enter Your Reply

The Comment You're Replying To
Michael Nelson wrote on Wed, Mar 30, 2005 08:14 AM UTC:
Peter,<p> If a piece is on a3, a LL on a6 can capture it by leaping to a2 or a1 and having the choice is quite valuable to the LL--one square may be attacked while the other is safe, one square may set up the next attack while the other doesn't, etc. <p> Now let's look at the case at hand: LL on x3 to capture x2 on x1 or x0. The amended rule constrains the LL's choice of captures when it is already very hard for the LL to capture a piece on an edge square--the LL must reach the edge via another capture (either previous or subsequent) <i>of a piece adjacent to the edge</i>. Only the LL (or a Chameleon attempting to capture a LL) is so restricted: A King, Pawn, Advancer, Withdrawer, Swapper, or Chameleon capturing anything other than a LL can capture a piece on an edge square <i>from an interior square</i>. <p> So the LL is uniquely constrained in its ability to capture an enemy piece on an edge square by board geometry and the edge rules, and the proposed rule would constrain it yet more. I feel that this additional constraint is foreign to the original intent of making it harder to hide from LL's on the edge. The Withdrawer isn't so badly affected as it is restricted in only two of its five possible capture directions when capturing a piece on an edge square, but if the LL is to have free choice, the Withdrawer should for consistency.

Edit Form

Comment on the page Rococo

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.
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.