Check out Grant Acedrex, our featured variant for April, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Sat, Nov 14, 2020 12:50 PM UTC:

Great, you did it! I would recommend to use the 'ferz' image for the advisors, though, rather than the pawn image.

And one remark: wouldn't it be better to swap the Ox and Elephant in the initial position? It is likely that you would want to use the Ox to build a King fortress that is 'Cannon proof', as it cannot cross into the other half to be used for offensive purposes. In the current setup it would take two extra moves to get the Ox there, which is a bit annoying.

You put the Elephant and Rhino in a very unfavorable start location anyway; they have no moves before you move up a Pawn. And even then they would end up behind that Pawn, their forward moves blocked. I know this is the same for the Elephant in Janggi, but there you can more easily move Pawns, because these also move sideways on your own half. The Elephant and Rhino are very clumsy pieces; even the pure leapers (Zebra and Camel) are hard to manoeuvre because of their large stride. And that they are easily blocked, often on squares that block two moves at once, makes it far worse. So perhaps you should give them the most favorable starting location that is possible, making the back-rank Rook, Horse, Rhino, Elephant, Ox, Adviser, King, ...


Edit Form

Comment on the page 中象棋(Middle Xiangqi)

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