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 05:05 PM UTC in reply to H. G. Muller from 04:14 PM:

that initial legs would behave differently from only legs.

The behaviour is the same if you stipulate that all slider legs are potentially 0‐length but null moves are disallowed unless explicitly specified

Perhaps we have different intuition

May well be :) And fwiw I'm fine with either system in practice

When 0 steps is allowed, you would need [F-fF-fB] for the Tamerlane Picket

Or simply [nA-fB], which to me looks more natural as an alfil extension (istr Gilman classes it that way too). [F-fB] is ofc a bit odd as a Bishop description, but there are always going to be strange ways of notating things

BTW, [W?sfNN], and even [W?sfCC] work now. All through using a new, undocumented (and quite horrible) extension of XBetza.

That's pretty cool :) (and agreed, the repeating ys are… not pretty). I can even get an offset giraffe‐rider (or even zemel‐rider — presumably longer ones work too, if they'd fit on the board), even though normal giraffe‐riders (FXFX?) are apparently unsupported!

But the y extension still fails for e.g. [W?sfZZ] (also shouldn't that be fsNN ⁊c?), let alone pathological things like [C?fsZZ], so if we're making an effort to support direction‐type changes it probably deserves to be more general.

Also speaking of the Z, [Z?sfB] currently gives me Zebra‐then‐Rook, and vice‐versa


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.