Check out Makruk (Thai Chess), our featured variant for March, 2025.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Fri, Apr 4 03:44 AM EDT in reply to HaruN Y from Sun Apr 28 2024 03:56 PM:

@HaruN Y

Thanks for the Diagram on this one. I was thinking about equipping the in-hand soldiers with all kinds of distant leaps from 9th rank, or situating those on extra 5th-rank squares left and right with an s(mpoa)mR move. But restricting mU with a morph is much simpler. Declaring the in-hand soldiers iron to remove the need for a gap between those and the board is also a trick I had not thought of.

P.S. It did need promoZone=2 for the white promotions to work. And it revealed a bug in the script, as the General was considered royal despite the fact that it was not mentioned in the royal=K. I suppose the problem is that a royal parameter menitioning the pieces by ID rather than number can only be processed after all piece definitions have been read, while with a number they set the royalness variables immediately. So defaulting the last-defined piece to royal in none is yet defined appears to happen too early.


Edit Form

Comment on the page Synochess

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.