Check out Symmetric Chess, our featured variant for March, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Wed, Feb 1, 2023 02:07 PM UTC in reply to Jean-Louis Cazaux from 12:53 PM:

Capablanca Chess and Carrera Chess have BN and RN singletons in the wings. For a board this wide I think it can even be nice to spread out the 'power-pieces' a bit. I don't have any clear preference myself; I just put RF and BW where I did because that was where Kevin had put the Elephants that I replaced. But I don't see why this would beg for 'improvement'. If symmetry would be the holy grail, I would sooner take two BW in the wings than move singleton BW and RF to the center. (BW on 16x8 could be significantly stronger than Rook anyway, because it will in general attack the opponent in two places, rather than one.)

One point to consider is that there are already so many variants using Elephants, Cannons, and Vaos (to not even mention Archbishops and Chancellors). I experience it as very refreshing to also see some other pieces now and then. The WA, FD, BW and RF are only rarely encountered, outside shogi variants.

And as to 'unnatural moves': if a chessplayer would consider anything unnatural, it will be the Cannon and the Vao. The presence of those divergent hoppers really upsets everything you thought to know about tactics. And I don't think the FD is unnatural at all: it is just the conjugate of a King (i.e. the 45-degree rotated version moving on the sub-grid of one shade). And King moves are very natural. The WA is indeed a different matter; you will have to learn how to manouevre with it, just like novice chess players have to learn to manouevre with a Knight. But that seems a small matter compared to mastering the use of Cannons and such.

I don't see much fun in reducing every chess variant to a version of Shako or Pemba on a differently shaped board.


Edit Form

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.