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

Enter Your Reply

The Comment You're Replying To
Gerd Degens wrote on Thu, Apr 21, 2022 09:24 AM UTC in reply to H. G. Muller from 07:54 AM:

"A Bishop on a4 could move along c5-d6-e7-f8 but not b5-c6-d7-e8. For a Bishop on 4 the reverse would be true. But that also means a Bishop on a4 can only be captured from c5 -d6-e7-f8 and not from b5-c6-d7-e8.

If this is true the ...."

This is absolutely correct when considering the squares of a switch as separate squares. This looks different if the switch is seen as a unit. But that's a convention that needs to be met. I have already described my intention, but it is not an absolute requirement.

"The issue of teh Knight is really an independent one. If the Knight's move is defined 'subtractively', by excluding moves that a Queen can do, its mobility is reduced in the vicinity of the switch, as Q gets extra moves there. In a 'constructive' definition of the Knight move, it would benefit from the switch topology to get extra moves as well."

Exactly this consideration speaks for a separation of the fields 4/a4. A knight starting from 4 via a5, a6 lands on b6. With a switch as a unit, b6 is on the same line. With 4 as a separate square, b6 is not on the same line. For a4 vice versa. That would be my consideration. I'm thinking of novice players who will notice exactly this inconsistency.


Edit Form

Comment on the page Chess 66

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.