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 Fri, Dec 10, 2021 09:40 PM UTC in reply to Daniel Zacharias from 07:38 PM:

What about using the brackets alone to indicate that all the moves contained within are part of a sequence? [FfR] [smpWsR]

Well, for practical reasons I would prefer to have some separator between the legs. (Then I can just use the JavaScript split method to split the move in the parts between the hyphens, while otherwise this should be judged by the case of every individual letter.) I think that once you allow the brackets, allowing other non-alphabetic characters as well is no longer a problem.

The idea of considering a certain grouped sequence of directional modifiers plus atoms as a 'crooked atom', and allowing the whole group to be prefixed, does have merit, however. Otherwise you would have to specify a separate move for each leg the mount could be in to make a hopper. E.g. for the Grao you would need [pF-fsR][F~fspR] (i.e. mount either at the F square or in the Rook path). Then p[F~fsR] is a lot simpler. The Interactive Diagram internally already uses this method for moves like zB and qN: it creates a complete description of the maximum-length path as a sequence of 1-step legs, with in each leg a special mode flag to indicate the move can also terminate there. And it does allow the entire path to be used as a hopper, in order to allow zpB or zgB. I could easily extend that to allow user-defined paths.

And you are right: the entire Griffon move is essentially an oblique slider, like the Nightrider. So it does make sense to allow indicating the individual trajectories by the same direction system as the trajectories of the Nightrider (or Knight). So the Ship would be the 'Narrow Griffon', like vN is the Narrow Knight.


Edit Form

Comment on the page Betza notation (extended)

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.