The Chess Variant Pages



Check out Marseillais Chess, our featured variant for February, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Mon, Jan 2, 2023 01:51 PM UTC in reply to Jean-Louis Cazaux from Sun Jan 1 03:23 PM:

Jean-Louis Cazaux wrote on 2023-01-01 UTC

To HG: Sorry to insist, I had no answer/reaction.

I think that it is not correct to change the name of the pieces of someone else's game, even for an editor.

Here Dog/Jolly Jumper/War Elephant have not been given by Betza.

If you don't want to remove those names in this page, you should at least insert a comment explaining for the readers who has named the pieces as such.

Well, this did not have a high priority, and I have been quite busy.

Although I admit that 'Jolly Jumper' was perhaps over-doing it, some of what you say here is not so obvious. Betza's contributions to the chessvariants community have been immense. But assigning names to pieces was not really his forte. And it is not uncommon at all for CVP editors to object to publication of new submissions because of improper naming of the pieces in their variant.

In the article at hand, Betza gives the move of the pieces, and refers to them by that. He does not give names, nor images. If, for the purpose of making a better diagram, I have to assign images, why not assign names as well. Especially in cases where the pieces with that move are well known, and do have established names. Like FD = Kirin, and NJL = NCZ = Bison.

Referring to the pieces like "FD (Kirin)" doesn't make much sense in the context of the Diagram, as the Betza notation for their move is already in another column of the piece table. I also do not list the Archbishop as "BN (Archbishop)".

So I will probably change the names to Kirin and Bison (is there a commonly used name for KA?), and perhaps add the remark that the diagram calls pieces by their usual names.


Edit Form

Comment on the page Chess on a Really Big Board

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.