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

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Sat, Apr 25, 2020 10:25 AM EDT:

That is the answer to my question. So if a virgin King is on h1, a black Bishop on h2, and a black Knight on g4, the King can move to h3. If his own Bishop was on h2 instead, he could not.

I have programmed Metamachy, and I believe the rule is the same in Zanzibar. Apart from the King never starting on h1 and so never being able to move two spaces from h1, this is still incorrect. Assuming the King did start on h1, it could not pass over h2 to h3, because the black Knight on g4 is attacking h2. So, the King on h2 could not leap to h4 in this position. Also, replacing the black Bishop with a white one would not make any difference. What would make a difference is replacing the black Knight with a white Knight. With that change made, black would not be attacking h2, and the King could leap from h1 to h3.

Personally this rule strikes me as quite illogical; to pass through a square it should be empty, and if you don't pass through it but jump over it, you shouldn't have to worry if you are attacked there.

This has to do with restricting the King's ability to move through check, which is borrowed from the restrictions on castling in Chess. Inspired by its use in Metamachy, I adopted the same rule in Fusion Chess for the Cavalier King's Knight leap.


Edit Form

Comment on the page Zanzibar-XL

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.