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

Enter Your Reply

The Comment You're Replying To
Thomas McElmurry wrote on Wed, Mar 30, 2005 12:05 AM UTC:

For the sake of posterity, here is a link to the game in question.

I see two logically independent questions here:
1) What should the rules be?
2) What is the correct interpretation of the rules as written?

The first question is relevant to future games of Rococo and should be answered by the inventors, taking input from the rest of us if they wish to. For the particular case of the present game, I think that the second question is relevant, and that ideally it should be answered by consensus.

The rules as written contain a general statement describing the concept of edge squares and their role in the game, and a specific statement for each type of piece, describing how that piece behaves with respect to edge squares.

The general statement:

These marked squares on the edge of the board are edge squares, and a move may only end on an edge square if necessary for a capture. Or in other words, a piece may only end up on an edge square by making a capturing move that would not be possible without landing on the edge square. This includes moves that start on edge squares.

The specific statement for the Long Leaper:

It may end its move on an edge square only when that is the only way to make a particular capture.

As I read these rules, the only thing that could be construed to forbid my move to x0 is the definite article in the second sentence of the general statement. It's worth noting that David's interpretation, based on this definite article, is paradoxical (as Mike Nelson has pointed out), and that the definite article only appears in a sentence which is presented as a rephrasing of the previous sentence. The first sentence of the general statement and the specific statement both imply (in my opinion; there may be some room for debate) that one edge square is as good as another. Since I can't capture the black Leaper by moving to an interior square, x1 and x0, both being edge squares, should be equally permissible under the rules as written.

Peter's emendation of 'landing on' to 'landing on or passing over' does produce a well-defined rule, but in my opinion it is inconsistent with the intention of the edge squares. If the black Leaper were on x3, then this rule would say that I can capture only by moving to x2, not x1. But a piece on x1 is no safer from a Leaper than a piece on x2. On the other hand, a piece on x0 is safer, so it would seem reasonable to forbid capture on x0, not because it is not the first square beyond the victim, but because it is on two edges rather than one.

In fact, I think this was Mike Madsen's understanding of the rules. (I hope he'll correct me if it wasn't.) While I maintain my belief that this is not the rule as written, it seems sensible, and in my opinion would be the best rule for the game. It could perhaps be stated most easily by defining three classes of squares (interior, edge, and corner), and forbidding a piece to move to an edge square except to make a capture which cannot be made by moving to an interior square, or to move to a corner square except to make a capture which cannot be made by moving to an interior or edge square.


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.