The Chess Variant Pages




[ Help | Earliest Comments | Latest Comments ]
[ List All Subjects of Discussion | Create New Subject of Discussion ]
[ List Earliest Comments Only For Pages | Games | Rated Pages | Rated Games | Subjects of Discussion ]

Single Comment

Fantasy Grand Chess. Variant of Grand Chess with different armies and fantasy theme. (10x10, Cells: 100) [All Comments] [Add Comment or Rating]
H. G. Muller wrote on 2021-05-08 UTC

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.