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

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Tue, Sep 23, 2014 07:36 AM UTC:
First of all, thanks for all your input! There were many things I would
never have thought of. Now some conclusions (mainly thinking aloud):

It would probably be good to treat 'gating', where introduction of a
piece takes places in combination with moving another piece, distinct from
true drops, which leave the remainder of the board unchanged. For gating
there is the choice to consider it as a side effect of the move of the
piece that was already on the board, and this seems the most convenient way
to do it. (In my Betza 2.0 proposal I had already introduced a move
modality 'u', which could unload something on the square indicated by the
Betza 'atom' to which it was prefixed.)

The true drops could be considered a special kind of Betza atom, and '@'
would be a good notation for it, as in standard algebraic notation drop
moves are written with it (e.g. P@c6). Dropping on empty squares only could
be written as m@, with the usual Betza modifier m. The power of Betza
notation is in clever choice of defaults, however. Where board moves almost
always have modality mc, which is thus default so it never has to be
written, it is very unusual to allow capture through drops. So for the @
atom, m could be defined as the default modality.

Then there is the concept of the 'drop zone'. In cases where this zone
consists of a few squares scattered over the board, there seems no
alternative to actually listing them. In Betza 2.0 I introduced the idea of
a 'limiter', which could be put on a modality modifier, like c{N,B}A for
a move that could only capture Knights and Bishops with an Alfil move. This
is a bit of an awkward notation, however, so for the more common cases,
where the drop zone is the entire board with the exception of some ranks at
the edges, I would like to have something simpler.

One method would be to write the range of ranks where the piece can be
dropped, e.g. 1-7 for Shogi Knights. This conflicts with the use of the
dash as chaining operator in Betza 2.0, however. It would be nice if we had
to write only a single rank number, for then we could write it behind the
atom: @7. This has similar syntax to W4 for a range-4 Rook. In fact it
would allow a similar interpretation, when we see the drop move as a move
that starts just in front of the board (on rank 0, as it were), on an
arbitrary file, and slides forward from there onto the board. The number
behind @ would then indicate the maximum rank it could reach. Like in the
Bex proposal for extension of Betza notation, a leading 0 on the number
could indicate it does not specify a maximum, but an exact number: @08
would mean 'drop on 8th rank only'.

Problem with this is that it is difficult to exempt a low rank from
dropping, as is needed for Crazyhouse Pawns, which can only be dropped on
ranks 2-7. This would then need an exhaustive listing @02@03@04@05@06@07,
which is pretty ugly. The problem is similar to that of 'skip-sliders'
like the Heavenly Tetrarchs of Tenjiku Shogi, which move as a slider after
skipping the first square (e.g. t(D,R) = D, then R in original Betza
notation). Another problem is that the dropped piece should be able to
reach any empty square within the range, even if there is blocking. IIRC
original Betza notation described a piece that could jump an arbitrary
number of obstacles with a 'jj' prefix. So mjj@7 would do it for Shogi
Knight drops.

Like the 'm', the 'jj' could be made default in absence of an explicit
single 'j' or 'n'. This offers the interesting possibility to specify
'non-jumping drops' n@8, which could drop anywhere upto the first
obstacle, but not beyond it. Such a drop mode was not mentioned here, but I
could imagine it would be a useful restriction on drops, to not make them
too aggressive. A drop on ranks 2-7 could be written with the Betza
'then' notation as t(@02,jjR5), i.e. initial drop on rank 2, followed by
an arbitrary jumping forward Rook move of upto 5 squares. Still not very
elegant.

There seems to be no obvious way to specify further restrictions, such as
on the number of Pawns per file, the number of color-bound pieces on the
same color, etc., in the Betza spirit. Perhaps some extra modifiers could
be introduced for such restrictions, but the available letters are already
almost exhausted. Because directional modifiers make no sense on a drop,
they could be reused for other purposes there. (It is already the case that
the meaning of directional modifiers depends on the atom that follows;
'fr' in frW means something different than in frF or frN.) So 'f' could
be taken to mean the drop is not allowed if there is already a piece of
that kind on the file, and 'b' that it is not allowed if it is already on
the board. 'ff' could be taken to mean there can be upto 2 on the file,
etc. 's' could similarly stand for 'same color square'.

This would make Shogi Pawn drops f@8, Shogi Knight drops @7, Tori-Shogi
Swallow drops ff@6. Hey, that is not so bad!

Edit Form
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.