Check out Janggi (Korean Chess), our featured variant for December, 2024.

Enter Your Reply

The Comment You're Replying To
Bn Em wrote on Sat, Dec 11, 2021 01:06 AM UTC:

I think Betza suggested also other uses for the brackets, like z[F,W] for a slider that alternats W and F steps in a crooked way, but this distinction could also have been made by using other separators than comma for that, e.g. [W/F].

He did indeed. The alternation modifier was in fact a, contrasting q which alternated circularly if followed by a set of brackets; t is also defined there, as is g (for ‘go’ — equivalent to the proposed [X-Y] to t[]'s [X~Y]) which covers the mao case (though conflicts with the Grasshopper usage).

writing the Griffon as F&fR or [F-fR] assumes the move can also be terminated without making all its legs, after just the F step.

There is technically another interpretation which would not conflict with the mao (and would obviate the need for Betzan g[] in the common case — though the original rhino (mao+wazir) would still need either the distinction or expliit compounding), which you've mentioned before: consider slider legs to move 0 or more rather than 1 or more, while leapers are still exactly 1. The arguably more complex piece that follows a gryphon's path but must move at least two spaces then gets a suitably more complex notation (e.g. Betza‐style t[FWR] or the like). This would also allow e.g. Tim Stiles' doubly‐bent Fox to be trivially t[WBW]. Of course with still more complex paths (t[WFR]?) the same considerations apply, though counting to 3 or more starts to be complicated for humans too so more specific notations of the likes of what are being discussed here are probably in order anyway.

What if doubling a direction made it absolute instead of relative?

As HG points out, duplication is already in use for other things; but in principle one could add a punctuation mark (maybe an apostrophe or an exclemation mark) to mark a direction as absolute rather than relative, which would be roughly equivalent

considering a certain grouped sequence of directional modifiers plus atoms as a 'crooked atom'

This is the interpretation I've been coming to for most chess‐variant pieces in general. Some kind of (for me, radial‐step — Nightriders have more in common with Dabbabariders than with Rooks imo) path and, independently, a set of constraints on that path, be it leaping, limited range, skipping squares, hopping, etc. And modality (movement, capture, or other special effects such as relaying or rifle‐capture) as a third factor on top of that. Works for most of the pieces people actually use afaict.

So the Ship would be the 'Narrow Griffon', like vN is the Narrow Knight.

I second this and the v[F-R]‐or‐equivalent notation, if a bracket‐style notation is being adopted, and if it's easy p[F‐R] and the like look nice too.

Worth noting as well that Betza also made a similar extrapolation in defining the a[WF]4 on the above page (just above the Two Sets, Four Boards heading)


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.
Avoid Inflammatory Comments
If you are feeling anger, keep it to yourself until you calm down. Avoid insulting, blaming, or attacking someone you are angry with. Focus criticisms on ideas rather than people, and understand that criticisms of your ideas are not personal attacks and do not justify an inflammatory response.
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.