Check out Grant Acedrex, our featured variant for April, 2024.

Enter Your Reply

The Comment You're Replying To
Bn Em wrote on Sat, Dec 11, 2021 01:23 PM UTC in reply to H. G. Muller from 12:46 PM:

True, but isn't 'intuitiveness' all about catering to human peculiarities?

I think here it depends strongly on which humans and in which context; after all most multi‐leg movers with slider components do have the option of zero‐length stages — GraTiA's gryphon/anchorite and Mideast/Rennchess' duke/cavalier are very much the exception afaik, so from a design (and usage) perspective the 0‐step leg option seems to be the more intuitive. The case with reading descriptions is slightly different, because you have to say both stages of the move and consciously we count starting from 1 (unless we're mathematicians or programmers), so it often requires being explicit in the verbal description.

[…] that in all kind of other cases people will get extra moves because they did not count on a slider leg also eliminating itself by taking 0 steps.

Oþoh I can see the other case where someone expects to simply be able to write e.g. [B-fW] for a transcendental prelate/contramanticore, and is confused by the fact that it disallows the W squares; ofc in this case it's simple to add them by hand (the ? notation doesn't handle this case) but with more complex moves it may not be. Whereas imo in the opposite case, where the contramanticore has to make at least a knight's move, it's likely to be more readliy apparent that an extra F step is needed at the beginning to force that (or indeed two or three extra such steps if necessary). And surely it's more intuitive to specify three initial W steps (after the F one ofc) for the Tamerlane giraffe (“one diagonal and then after that at least three straight”) than only two?

Reminds me a bit of regexps; the Kleene star * there does explicitly specify 0 or more and if you want a minimum n^r of repetitions you have to specify them explicitly (or use syntax extensions like +)


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.