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

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Fri, Mar 18, 2011 09:49 PM UTC:
Okay, I've now remembered why Hex Shogi uses horizontally-aligned hexagons rather than vertically-aligned hexagons. Using horizontally-aligned hexagons modifies the movement of every piece in Shogi, whereas using vertically-aligned hexagons leaves the movement of some pieces unmodified, which creates a greater disparity in value between the pieces with additional powers of movement -- such as Rooks, Bishops, and Kings -- and those without, namely the Pawns, Lances, and Knights. Although I wasn't aware of it when I created Hex Shogi, George Dekle adapted Shogi to a vertically-aligned hexagonal board in 1986 and called his game Hexshogi. His is a more straightforward adaptation of Shogi to a hexagonal board, but I expect the weakness of the forward only pieces makes it more drawish than my game. In fact, it includes rules for counting pieces and declaring a winner when the game is at an 'impasse,' which I take as an indication that even the inventor found the game drawish.

Also, the use of the same board as Glinski, McCooey, and Wellish used is an afterthought. Hex Shogi was originally designed for a board with 41 spaces, and it is only after I had formulated the rules for the game that I selected some more suitable boards for playing it on.

Edit Form

Comment on the page GraTiA

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.