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

Enter Your Reply

The Comment You're Replying To
Tony Paletta wrote on Sat, Dec 13, 2003 07:37 PM EST:
Fergus,

My argument for not FOLLOWING the convention for using 'orthogonal' and
'diagonal' on hex grids was not based on the idea that they were not
CONVENTIONS,l but that they did not have the same FULL MEANING as on the
chessboard (crossing edges at right angles, but also moving along paths
that are at right angles), which in turn did parallel the more
comprehensive meanings used in mathematics (as opposed to the less
specific 'at right angles' dictionary entry). Both Dickens and Parlett
were well aware of the existence of hex games such as 'Hexagonal Chess'
and gave definitions that covered both -- they were certainly not out to
fight the convention, but simply to reflect it.

One point of my usage (edge-paths, rather than orthogonals; point-paths
rather than diagonals) is that it avoids the terminology problem for
pieces that demonstratably move exactly like chess Rooks, chess Bishops,
chess Knights, or any chess piece) in games on a hex-tiled board. The
conventional chess pieces follow the paths that reflect conventional chess
patterns; the hex pieces simply follow different paths. The baggage of
definition by analogy from chess (orthogonals into hex-orthogonals;
diagonals into hex-diagonals) disappears if the partial analogy is not
followed.

Edit Form

Comment on the page Constitutional Characters

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.