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

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Thu, Apr 6, 2023 05:56 PM UTC in reply to Max Koval from 04:13 PM:

[Editor's Note: This was moved from the same page as the previous comment.]

When you play 1.e5 in Shafran's chess, after black's response you can move your bishop to e2 and then attack both black rooks simultaneously. This leads to forced defensive progressions like b5 and h8 (the black knight won't work due to a3). It's roughly like playing 1.e4 a6 and h6 in orthodox chess. After that, you may want to move like a3 or h8, and after exchanges end up with an open vertical.

I don't think b4 and h8 are similar to a6 and h6 in orthodox Chess: these moves open a ray for the Rook, and increase mobility a lot, while the latter even reduce the number of moves. I don't see any forced gain of material here yet, although it is clear that this deserves some investigation. But even if a positional advantage can be forced by white here, calling the variant 'unplayable' because of that is a bit like equating having to shelter in a celler while a rain of rockets reduces the city above you to rubble to the discomfort of having a mosquito in your bedroom...

Nevertheless, I think your remark on this weakness deserves to be mentiones in the Shafran's Hexagonal Chess article.

Edit Form

Comment on the page Shafran's 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.