Bn Em wrote on 2021-12-16 UTC

the same trouble with the bishop and queen.

It's not entirely clear what the analogous ‘error’ would be. In the REX King's and Glinski Pawns' cases it's using orthogonal moves to the exclusion of hex‐diagonal ones, while this knight apparently just miscounted the diagonal portion, resulting in a piece (which Charles Gilman terms a Student) which is analogous to the square‐cell Zebra.

A queen analogous to the REX king just becomes a rook, but that leaves the bishop completely unaccounted for.

Ofc, there are a few variants which take this version of king and queen as their basis and build the rest of the pieces around them: the oldest is Sigmund Wellisch's 3‐player game (for which this site unfortunately has only a Java Applet, though a more complete description is available e.g. on John Savard's page); the king moves one orthogonally, the knight to any nearest square that the king can't reach (there is a certain logic to calling the hex diagonals ‘leaps’, given that the relevant cells don't actually touch), the rook slides orthogonally, the queen moves as rook or knight (technically a marshal analogue therefore), and the pawn in either of the forwardmost directions (the board being oriented as in Fergus' Hex Shogis).

Alternatively, Gilman's Alternate Orthogonals Hex Chesses do exactly what the name suggests: assign alternate orthogonals as analogous to the square‐board directions, giving a REX king and Glinski pawns together with Wellisch knights, a rook as a ‘queen’, and ‘rooks’ and ‘bishops’ which have each other's move but backwards — albeit this being Charles Gilman, the pieces all have ifferent names. This one had quite a positive reception, and it does preserve some aspects of square‐cell chess that other analogies lack (some of which are touched on in its comments) — it's certainly worth a look

Edit Form

Comment on the page Treyshah

## 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
• An URL by itself:

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

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