Check out Alice Chess, our featured variant for June, 2024.

Enter Your Reply

The Comment You're Replying To
Mark Thompson wrote on Wed, Jul 9, 2003 08:57 PM EDT:
Personally, I prefer names that are 'real' nouns, but chosen with as much
logic as possible. For instance, a Queen isn't called a Rook-Bishop, so I
feel a Marshall shouldn't be called a Rook-Knight. The room this leaves
for logic isn't very great, but I'd be inclined to give, for instance,
names suggesting greater importance, authority, or strength to pieces that
are more powerful: for example, 'Empress' would be a reasonable name for
Q+N, but not for (say) B+N. I would give clerical names to pieces whose
chief move is diagonal, such as 'Priest' to a one-step diagonal mover
(um, that's a Ferz? or an Alfil? I can never remember). I like Cardinal
for B+N, and would use Archbishop for a Bishop with a one-step orthogonal
move. Animal names are well reserved for leaping pieces like Knights,
Camels, Zebras, etc.

But the problem with all this is that there seems to be no way to get
everyone to agree to use the same terms, and some pieces already have
several different names that each have considerable tradition behind them.

Edit Form
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.