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 Mon, May 7, 2012 06:14 AM UTC:
Sorry not to get back to you earlier on this, Jörg. It's good to see your approval. Wyvern does clash with Beastmaster Chess, but then so does Pegasus (which I use for a Bent piece). I do not completely rule out replacing Wyvern, but it will not be easy. It is quite difficult to find names that don't have internal clashes, and I had chosen Wyvern because I had previously underused names using Y as a vowel. An added complication is that my convention for 8:6:n cubic pieces is to reverse the 10:n piece name, so Replacing Wyvern would also require replacing Nrevyw with another non-clashing name. Of course the combination of R and I is now free, as would be that of R and U were I to rename the 8:3:2 leaper Sugarglider - a kind of marsupial to go with Dunnart. That however would in turn require a new name for the root-61 pure-hex leaper - I was never satisfied with Suntrap but am still struggling for an alternative to it. Turning to forward-only leapers I have managed to preserve the initial letters of the 7:4 and 8:1 forward-only leapers, and would prefer to do likewise with the 10:7 one and still have a name fitting in with whatever I settle on for the symmetric one. Had I remembered Beastmaster Chess I might have used one or more of the names from that for the same pieces, but substituting them for the names that I ultimately chose - n:4-n Caribou, n:5-n Gamewarden, n:6-n Trampler, n:7-n Swan, each prefixed with End- to add the orthogonal leap - would have too many knock-on effects for other compound pieces.

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