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

Enter Your Reply

The Comment You're Replying To
Charles Gilman wrote on Thu, Aug 6, 2009 05:59 PM UTC:
I recognise the piece called a 'Rook' here. The idea of a piece moving straight forward/backward/sideways on a hex board was put to me when I claimed that there was 'no piece bound to half a hex board' although the Dabbaba is bound to a quarter of it. I eventually documented it in my piece article Man and Beast 12: Alternative Fronts - you can find it by searching on that page for Moorhen. It is defined by the straightness of the directions (and of up and down on a hex-prism 3d board) regardless of whether they are orthogonal or hex diagonal and whether the orientation is Wellisch, Glinsky, or hex-ranked.

The labels for the directions are somewhat confusing as 'oblique' usually indicates a direction such as that of the FIDE Knight, going through intervening cells off-centredly. A more accurate description for the directions of each colour are forward/backward hex-diagonal, sideways orthogonal, forward/backward orthogonal, and sideways hex-diagonal. The linepieces in these directions I term Unicoranker, Rookfiler, Rookranker, and Unicofiler. These definitions also work on a Glinsky board, but on that it is the first two that have four directions and the second two only two.


Edit Form

Comment on the page Hex Dragonal 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.