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

Enter Your Reply

The Comment You're Replying To
Greg Strong wrote on Wed, Apr 28, 2021 01:14 AM UTC in reply to H. G. Muller from Tue Apr 27 09:25 AM:

Your variant poses the problem that both the King destination and the castling partner have multiple options. This requires specification of two squares. A possibility would be to let the empty square where the King should move to capture the Rook. (Or have the castling partner capture itself, when the King would end there.) Perhaps Greg has ideas of how to best solve this.

I don't really consider this a "castling" problem.  What we have here is a rule where multiple combinations of pieces can move to multiple combinations of squares.  There could be use in addressing this for any game might want to do this, but if we want to support this, I think it should be done in a general way, not forced into the context of castling.  (So, I am not at all in favor of empty-space-captures-rook.)  I think the robust way to address is as two separate moves, like "a1a2,b1b2".  Doesn't the interactive diagram have a similar issue with the Forest Ox from Odin's Rune?  It also must record a third square.

Also, if we're going to do an a1a2,b1b2 kind of thing, it makes sense to me to consider a separate delimiter for multi-move games such as Mersaillias.  I think our life would be easier if "single moves" that consist of different parts are delimited differently than the separate moves of multi-move variants.  For example, if a double move variant has, as it's first move, one of these moves that requires two different annotations, perhaps something like "a1a2,b1b2;c1c2"

In any event, this is a large can of worms, and I don't think we rush a poor solution just because this expiremental game has a crazy castling rule.


Edit Form

Comment on the page Interactive diagrams

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.