Check out Grant Acedrex, our featured variant for April, 2024.

Enter Your Reply

The Comment You're Replying To
Christine Bagley-Jones wrote on Sat, Feb 5, 2011 04:21 AM UTC:
Oh if u mean no original alfaerie for 'sky' then yes there isn't but i am very used to the ones i used, u don't really see them too much in games either. On the download zrf page for 'sky' is info on game and at the bottom of the page there are graphics of pieces and the name and movement given.

Charles, naming pieces, i know u have a 'big production' going on there and changing one name means changing a lot of others, so, yeah, it's a problem, and i think u should name them what u want. But if u could not name an 8-1 leaper 'ibis' it would probably be good seeing that name is connected with a 5-1 leaper from at least 1999 it seems. It would be confusing. If u havn't already named it that, u could consider, or at least on your page mention that some people call 5-1 leaper 'ibis'.

But then again, as we see, people name pieces what they want disregarding names that they were called earlier. Who invented the compound pieces 'knight/bishop' and 'knight/rook'? What were original names?

Tai Shogi has an 'alfil/wazir' called 'Phoenix' (Hoo) and another piece called 'Kirin' that moves 'dabbaba/fers' Surely these pieces were the first ones invented?

Edit Form

Comment on the page Sky

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