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

Enter Your Reply

The Comment You're Replying To
Charles Gilman wrote on Mon, Mar 5, 2007 08:26 AM UTC:

You have miscounted the cells. There are only 91, the same number as in the three historic hex variants, not 109. In view of this, do you still think that there are too few pieces for them? What about in the 3-player variant?

Regarding notation, the secojnd array is 3-player and there are not three cases of letters to distinguish them. Single letters would be confusing if I use this method for a wider range of hex variants - rather than my previous practice of having a ffen diagram for the 2-player array and leaving readers to work out the 3-player one for themselves! I would be interested to hear which you think preferable.

Those apart you make some good points. I never said that Viceroys were a good Knight analogy, but they are a historic one. It has just struck me that on the Glinsky/McCooey orientation one way to make unbind the piece would be by adding an extra move directly forward, either a single or a double step. Which would be better, do you think? Such a piece could be reduced in number, and the Rooks increased, to two. The names Forerook and Hindrook were thought up fairly quickly, and if you can improve on them while retaining the ease of extrapolation I'll happily listen to your ideas.


Edit Form

Comment on the page AltOrth Hex Chess

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.