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

Enter Your Reply

The Comment You're Replying To
Dave McCooey wrote on Fri, May 26, 2006 11:40 AM UTC:
To clarify, Glinski's pawn capture does not advance the pawn one step
closer to promotion as in regular chess.  It advances the pawn 1/2 of a
step closer.  In my variant, a pawn capture advances the pawn 3/2 of a
step closer, so neither variant emulates regular chess perfectly in this
regard.

The diagonal pawn capture used in my variant allows pawn chains to behave
as they do in regular chess, which is not true of Glinski's pawn chains.

For example, it is impossible in Glinski's chess to have interlocking
head-to-head (blocked) pawn chains where the pawns can't capture each
other.  Try creating something equivalent to the following regular chess
pawn chain:  White pawns on f3, e4, d5; Black pawns on f4, e5, d6.  All 6
pawns are immobile, they cannot capture each other, and each side forms a
protection chain starting at an unprotected base pawn.  In my variant,
the
equivalent would be White pawns on g4, f6, e7; Black pawns on g5, f7, e8.

In Glinski's variant, it can't be done:  Either the pawns can capture
each other, or the pawns on each side don't form a protection chain. 
(Note:  I am labeling hexes using the bent-rank notation where the 1st
rank consists of the 11 hexes on White's edge of the board.  The hex in
the center of the board is f6.)

Edit Form

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