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

Enter Your Reply

The Comment You're Replying To
Charles Gilman wrote on Thu, Jan 1, 2004 09:35 AM UTC:
Michael Howe may have a point about promotion. I did consider promotion to one, or even a chioce of either, of the Shogi generals (to preserve the unpromoted Pawn's capturing move, of all things!), but I was trying to limit the modification to Xiang Qi promotion to that needed for a piece that does not get weaker and weaker as it moves further into enemy territory. Rooks and Bishops are just as strong WITHIN enemy ranks once they get there as they are WITHIN their own, they just have difficulty doing the actual crossing. Incidentally that includes coming back as well, in case it was unclear. A White Bishop on rank 5 cannot retreat in one move, but can block a Black Rook from retreating. Perhaps I should also have mentioned that a Bishop leaving a bank always puts the bridge back first, so that Rooks can move unimpeded once the Bishop has gone. This also means that if one army loses both Bishops the enemy Rooks can then move exactly as in FIDE Chess.

Edit Form

Comment on the page Anglis Qi

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.