The Chess Variant Pages

Check out Marseillais Chess, our featured variant for February, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Sat, May 8, 2021 01:17 PM UTC in reply to x x from 12:24 PM:

I dont think the wierd promotion rules for horde are implementable in the diagram.

You mean those of the Orc? That is indeed too weird. It is like a locust capture throuh a Universal Leaper move, combined with 'promotion' to an empty square (kamikaze capture). And it can only be done when the fF move can enter the zone.

Kamikaze moves can already be implemented throuh providing a JavaScript routine WeirdPromotion(). A cU move in combinaiton with a kamikaze WeirdPromotion would do it. Except that it would then be able to do it from any square of the board, not just when it ended in the zone. One can also provide a routine BadZone() to veto moves, but I think that doesn't get the from-square of the move passed as an argument. (I used it for zone confinement in Xianqi, but it can also be used to enforce type-specific capture as in Stratego.) Not sure if WeirdPromotion() can veto moves; it should not be difficult to allow it to do so. It could then test whether the Orc was able to enter the zone. It would not be able to distinuish a normal capture of the Orc in the zone from a 'promotion capture', but I assume one would never voluntarily 'explode' the Orc if it could capture normally. So the Orc could be defined as a non-promotion piece, but all Orc captures could be tested for being diagonally forward, and if not, result in suicide if the Orc could enter the zone.

Triple (or more) captures can be defined in XBetza, but the UI of the diagram currently has no way to enter those. This is still on the to-do list, but so far the Lion Dog from the large Shogi variants was the only piece that would need it. So it did not have a very high priority.

Edit Form

Comment on the page Fantasy Grand Chess

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.