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

Enter Your Reply

The Comment You're Replying To
Gerd Degens wrote on Wed, Apr 20, 2022 07:07 PM UTC in reply to Fergus Duniho from 03:30 PM:

You can agree on almost everything, certainly to make the game playable and programmable. Regardless of that, I can only say my point of view and describe my intentions.

"A switch is an overlapping pair of spaces that in some ways operate together as a single space."

From my point of view it looks different. The square a4 of a switch is an independent square and is completely identical to the square a4 in normal chess. 4 (A4) is a composite square consisting of a half and triangle part of a4 and the new triangle due to board geometry. The new square 4 (A4) gets the same play options as all squares of the game board - 4 (A4) is considered equal.

This means that the squares a4/4 (A4) must first be seen independently. These independent fields get an additional function when they work together and act as a switch, as described.

My intention is therefore not compatible with the proposal to merge fields 4/a4 (A4) as proposed by Jean-Louis.

It is possible to agree on the sides from which the switch should be accessible. We have clarified access from below and from the side, access from above is also not a problem and is already part of my proposal. The only question is whether it is access to the switch as a unit or to the individual square of a switch. According to my intention, the second applies.

"Allow pieces access to the spaces of a switch from any direction, and when a piece moves to a switch, allow capture of any piece on the switch even if the capturing piece moves to the other space. For example, if a bishop is on A4, and a Rook moves to a4, consider the Bishop on A4 to be captured."

As described, access to the switch from all sides is not a problem. It is possible to agree on the proposal, but it does not fit my intention. However, if the game becomes more playable and programmable - so what.

To the Knight: I can't allow anything here, but I can say what my point of view is. If we stick to the fact that the squares of a switch should be seen separately, then knight moves ending on the same line are not possible. However, as the game becomes more playable and programmable, compromises should be possible.

"One last rule change I would suggest is to let Rooks, Queens, and Kings use their ability to move horizontally to switch between the spaces constituting the switch. This would basically involve lifting one more restriction on movement to the spaces making up a switch. "

I have problems with that. I have emphasized that the squares of a switch represent independent squares. This would rather mean that moves between the squares of a switch are possible. The independence of the squares on the one hand and the functionality of a switch on the other compete with each other. Regarding the direct change between the squares of a switch, I tend towards the superordinate function, so a direct change should not be possible. At least that's my intention. But here, too, compromises determine reality.


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.