Check out Glinski's Hexagonal Chess, our featured variant for May, 2024.

Enter Your Reply

The Comment You're Replying To
Charles Gilman wrote on Wed, Feb 9, 2011 06:58 AM UTC:
I certainly don't write with the intention of being ignored. Indeed I positively invite feedback, on both the piece pages and the variants, and certainly hope that someone who enjoy implementing variants takes them up. If I don't implement them myself it is only because I'm such a perfectionist and don't have nearly enough time online to test the implementations to ensure that I don't make a real clanger of a mistake. Some of my variantys have been implemented too - even I'm a Wazir... which I consider the poorest of my surviving variants. Note that word surviving: the two worst that I ever posted, Heroic Round Chess and Voyager, have bitten the dust, although unfortunately the indexing still shows them, and many more even worse ideas of mine never even reached the stage of getting a page.

Incidentally, my welcoming of feedback is, I feel, another thing that distinguishes us, particularly when it comes to gaps in your own scholarship. For example, on the Alfil page, 'Golombek also points out that the English word elephant was also borrowed from another language. Although I can't document the connection, elephant does sound similar to alfil. Perhaps it has its roots in the name for a Chess piece.' starts off scholarly enough but then deteriorates into wild and uninformed speculation. Yet when an informed person informed you otherwise you ignored the help. True, I didn't cite a specific source, but any dictionary of Classical Greek would confirm it. If that's a bit too exotic, even a Latin dictionary would at least confirm that the roots of the word elephant go back long before Shatranj. When someone suggests an improvement on any of my contributions I give it consideration, make the change if inspired to, and even if I don't take the change on board I explain why and try to do so civilly.

It would be interesting to hear from a newcomer whether they do get the wrong idea that you describe. I have certainly attempted to highlight any established usages. I've been trying to get away from duplicating information on every page in favour of concentrating general information on the overview page. I'll certainly consider some rewriting of the intros, but I certainly wouldn't put in some gaudy monstrosity that takes over eighty characters to get to the first word and is at odds with my own relatively austere style.

Regarding your second comment, most of the issues that you raise are out of my control. What image is used for the Piececlopedia and which for piece articles is a matter for the editors. It can't help that piece articles are shown in such close association with the Piececlopedia. Better would be one paragraph marked something like 'Piececlopedia: a piece-by-piece reference on the use and naming of pieces used in historic and regional forms of Chess' and a separate one marked something like 'General piece articles: thoughts by individual Chess variant enthusiasts on groups of pieces in and for Chess and Chess variants', each paragraph with its own image writ large. As I say, though, that's a collective decision for the editors. As you are so keen to remind me, I no longer have editor status, and as it happens I wouldn't have time at present to make use of it if I still did.

Your X-men reference is entirely lost on me, as I do not follow the series. For example, to me Wolverine means this.


Edit Form

Comment on the page Index B to Man and Beast

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.