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

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Tue, Jan 12, 2021 03:28 PM UTC in reply to Greg Strong from 02:46 PM:

That is also true. But the Diagram has always used the convention that in combination with i, the n would create e.p. rights on the squares it can be blocked, to make it possible to describe a FIDE Pawn with an ifmnD component. And to make Metamachy Pawns possible, I later added the convention that nn had the same effect (i.e. not only make the move lame, but also rights-creating). So nnA would be a XQ elephant that can be e.p. captured (by fsmceW XQ Pawns...).

But the n had no meaning on the stepper atoms W and F, and their sliding multiples R and B. And the in and nn conventions are really unsatisfactory, because the n on which they are based is: they are ambiguous for oblique moves. XBetza solves the lameness problem by explicitly specifying the path through multiple W or F legs, with m-only capability on the intermediate squares where blocking can occur (and mp on squares that are jumped over). So it would be natural to also allow explicit specification of the squares where e.p. rights are created. And the n (which already had a similar meaning in the other contexts, albeit only after duplication) was available for overloading.

So nW now means creation of e.p. rights on the destination square of the W step (only meaningful on non-final legs, as otherwise the piece would remain there to be captured anyway), and nR or nW4 creation of rights on the destination of every W step that makes up the total R move. Together with the convention that c moves can always e.p.-capture royalty (and e is only needed to enable e.p. capture of non-royals that created rights), this makes it possible to use n for defining sliding royals that cannot move through check.


Edit Form

Comment on the page Play-test applet for chess variants

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.