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

Enter Your Reply

The Comment You're Replying To
Kevin Pacey wrote on Wed, Nov 8, 2017 06:59 PM UTC:

Hi Aurelian

As chess author Cyrus Lakdawala wrote regarding a position in his Slav book where Black just played ...Qxb2-pawn, after White offered it, "Anger flashes when our values are questioned". For what it's worth I have somewhat less invested in such discussions. My chess play does depend a bit on believing bishops are normally worth a tiny bit more than knights, though, so I do have some real skin in the game. In general I still wonder how much is up for debate on questions of piece values, at least on this website. Otherwise, H.G. has indirectly done me at least one big favour on the web in the past, in regard to my Sac Chess variant, so I try not to overdo things too much.

On another topic, I'm having a problem finding a suitable new minor piece type for a possible 10x8 variant that's close to being Capablanca Chess. In fact it's an impossible problem to solve, given my desires for such a piece. An elephant-ferz doesn't quite seem right, as though I do want the piece type to be symmetrically moving, I want it to be worth about a N or B on a 10x8 board, which I'm doubting in the case of the elephant-ferz, and I also ideally wish to place bishops on certain squares in the setup, yet have all pawns protected, and avoid possible common early exchanges of pieces from the start.. So far an elephant-wazir would be perfect, except it's hard to develop in the setup unless it takes a good square away from a knight, and in the setup I have in mind it would also guard the rook beside it, which somehow seems unattractive. The next best piece would be the guard, but it's a bit boring and also tedious to develop from the setup. The moral seems to be that sometimes you cannot have everything you want, even in chess variants, where you might even invent a piece.


Edit Form

Comment on the page King

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.