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

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Thu, Dec 22, 2022 09:25 PM UTC in reply to A. M. DeWitt from 08:23 PM:

Thankfully, this problem can easily be solved by writing the missing legs separately, yielding B(cpaf)2cBcafpafcBpafcafcB.

Ah, OK. This is what I vaguely remembered when I mentioned that combining destructive and non-destructive modes might cause problems. The Betza parser therefore separates those. But since this was written at the time only a single locust square could appear in the move encoding, it doesn't do a very elaborate job at it. The AI's move generator could perform this separation while generating; after every leg it calls itself recursively, for the remaining legs, and it could just call itself two times: once with and once without locust square. (It might not do that, though, because there was no need, as the parser already ensured that the combination would never occur.)

I will have a look at this; it must be possible to suppress the separation by the parser when NewClick is being used, and make the AI's move generator do it in that case. Up to then you indeed would have to do the separation yourself. Or at least part of it, keeping in mind that the parser only separates one of the legs. So you could write mpcafcafcBmpcafpafcB to specify all 4 combinations.

And no, paf should not be equivalent to mpaf in any case. paf must hop, mpaf is completely ignoring the square, 'seemlessly' gluing the legs into a longer leap. mpaf should not be used on slides: logically mpafB would mean mafBpafB, where the first term is the exploding version of B (a 'degenerate hook mover'), and pafB what Betza originally wrote as pB. So BpB would be the recommended notation.


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.