Custom Search

H. G. Muller wrote on 2016-10-02 UTC

The problem is that 'lame' is an ill-defined concept for 'oblique' moves (i.e. not strictly orthogonal or diagonal). E.g. look at the Xiangqi Horse (Mao). It is a lame Knight. But that in itself doesn't tell you that it can be blocked on the W; squares, rather than the F squares, like the 'Moa'. Or whether it is multi-path, and can only blocked by occupying both squares. So one has to specify the path, square by square.

This can be done by describing the move as a sequence of steps. The Mao takes one orthogonal step, followed by an outward diagonal one. This can be described by afsW: 'a' (= 'again') for indicating there are two steps, and 'fs' behind it to indicate how it bends. So the Mao is described as a two-step Wazir that bends 45 degrees after the first step. The default modality for the first step is 'm', (because another step follows), so it does not have to be written. The Moa would be afsF, and the Moo would be afsK, so it can start in any of the 8 directions.

The notation for the Falcon used here is an extension of that to 3 steps (so there are two 'a', each followe by two descriptions of how the trajectory bends). There are 3 path types: bend early, bend late and bend twice. E.g. bend early can be written as afsafK: the second step forward-sideway compared to the first, and the third 'forward' compared to the second. Unfortunately the twice-bent path has to be written as one left+right and one right+left path, as there is no way to indicate in the third step "now bend in the opposite direction". This is how I finally arrive at afsafKafafsKaflafrKafraflK.

The additional 'm' written in the diagram are really redundant, and act as a reminder only. For non-final leg 'm' is the default, like for a final (or only) leg 'mc' is the default modality. That makes the XBetza system tuned to representing lame leapers. Pieces that capture or hop on their way do need extra modifiers to indicate that.

Edit Form

Comment on the page Falcon 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
• An URL by itself:

### 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.

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.
﻿