Check out Chess with Different Armies, our featured variant for July, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Sun, Nov 22, 2020 05:25 PM UTC:

I think this variant has a design flaw. In orthodox Chess a Pawn protected by a Pawn is basically unassailable for any piece, except that Pawns can still successfully capture it (i.e. without losing material). But here that is no longer true: capturing a P protected by a P makes the latter promote in the recapture. This makes it too difficult to break down Pawn chains.

Maka Dai Dai Shogi, from which the promotion-on-capture rules were borrowed does not have this problem: the Pawns there are Shogi Pawns, rigorously bound to their file, so that Pawns can never protect each other. With FIDE Pawns the rule do not work so well, though.

One way to repair this would be to replace the FIDE Pawns with Shogi Pawns. This violates the spirit of the design, however, which was to use promotion-on-capture in a FIDE context.

An alternative would be to make PxP a special case, in which no promotion can take place. Other pieces capturing a P could still promote, as could a P capturing another piece.


Edit Form

Comment on the page Veteran Chess

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.