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

Enter Your Reply

The Comment You're Replying To
Kay wrote on Wed, Jun 15, 2022 03:01 PM EDT:

There's something a bit strange about the sandbox, and I'm not really understanding how it works. I wanted to try my hand at making a knight that takes 2 steps and bends 45° right after each move (sort of like a right-chiral Rose), and eventually what I ended up with is hlalfNhrarfN.

In other words, it's a knight that can either take a left-chiral step and bend to the left (???) or take a right-chiral step and bend to the right. Why do I have to specify that it continues left-forward? If you just look at hlalfN it behaves similarly to a rook that can only take 4 steps. But if it just took a left-chiral step and bends further to the left to take its next step, how does it end up back on the same rank or file that it started?

I can't make sense of why it works, or should work, like this. It seems arbitrary. A left-chiral version of this would look like hlarfNhralfN... so to specify a left-chiral one I need to go against the previous chirality and to specify a right-chiral one I need to use the same chirality?! There is no innate property of "right" and "left" that makes them unambiguously correspond to "same-chiral" and "opposite-chiral", so why is it implemented this way?


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.