Check out Janggi (Korean Chess), our featured variant for December, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Tue, Nov 28, 2017 03:59 AM EST:

Thanks for spotting the error. Betza notation was originally designed for indicating moves; (i.e. where a piece can end up relative to its current location), and not for specifying side effects. I admit that the XBetza extension breaks that rule by introducing the 'e' modifier for indicating e.p. capture. And the 'a' modifier for describing what are basically multiple moves per turn can in theory be used to describe side-effect captures, by having the piece jump around before it finally settles on its destination, trampling everything that should disappear first. In the case of the Fire Demon this could be done by having it encircle its final destination with steps that have mpc mode, except that this would make the capture optional, as the 'p' part allows you to jump over the opponent as well. In XBoard I solved this by an ad-hoc extension: 't' in a non-final leg ('tame') there limits any hopping to friendly pieces only. (In final legs I use it to specify a move cannot capture royalty.) So the mode mtpc would do it, and make the Fire Demon's move something like

gyafmtpcabrmtpcafmtpcarmtpcafmtpcarmtpcafmtpcarmtpcarB

and similar things for the vR and aaK components. (The 'gy' in the first leg changes the range from slider to leaper for the subsequent leg(s).) This does not seem really helpful as explanation, however, and the 'a' operator was never meant to be abused for this purpose. (And note that the interactive diagram currently cannot handle more than a single side-effect capture.) It would also not work at the edge of the board, because the FD would not be able to complete the detour there without falling off. This could again be solved by assigning a new meaning for the modifier 'o' in non-final legs, for legs that can step off the board. All intermediate legs should then have the mode mtpooc.

To be of any practical use, a notation would have to be far simpler. I have been playing with the idea to introduce a modifier for 'explosion', (say 'xx') indicating mandatory removal of all adjacent enemy pieces in combination with the mentioned ordinary modes. That would give move components like xxmcB for the FD, which is a lot clearer, and more in line with the philosophy of Betza notation. (I already used a single 'x' for another purpose in the diagram, namely move relay.) Captures of Atomic Chess could then be xxmcdN, etc., the extra 'd' (''destroy') indicating it also works for friendly pieces.

The problem is that this still doesn't give a complete description of the Tenjiku Shogi Fire Demon, as the latter also has passive burning ability, during the opponent's turn, which actually dominates the active ability. So the burning is actually more like a special game rule than a move description; every turn ends with removing your own pieces adjacent to an enemy Demon, and after that removing the enemy pieces adjacent to your own Demons, irrespective of whether the Demons moved or not. That would decouple the burning from the move.

 


Edit Form

Comment on the page Tenjiku Shogi

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.
Avoid Inflammatory Comments
If you are feeling anger, keep it to yourself until you calm down. Avoid insulting, blaming, or attacking someone you are angry with. Focus criticisms on ideas rather than people, and understand that criticisms of your ideas are not personal attacks and do not justify an inflammatory response.
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.