Check out Janggi (Korean Chess), our featured variant for December, 2024.

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Wed, Mar 11, 2020 06:28 PM UTC:

Based on my experiences with Zillions of Games, I think that the Dragon King is too tough to checkmate (and, perhaps, so are the Pope and Eques Rex).

I'm thinking of borrowing a rule from Metamachy for limiting the movement of the Eques Rex, which I'm planning to rename Cavalier King. In that game, a King may leap two spaces on its first move, but it may not pass through check. To make a Knight move, it must have an unchecked path to the space. So, I'm thinking of limiting the Cavalier King in that way. It could not make a Knight leap if both spaces adjacent to it and its destination were checked. However, this would not apply to checks from royal pieces. This would allow the Cavalier King to check another royal piece with different powers of movement.

Cavalier Chess handles the power of this piece by giving greater power to the other pieces, but in Fusion Chess, the pieces have the same total power as they do in Chess, and all that's different is having the ability to more fluidly redistribute power among the pieces. So, weakening the royal piece in this game seems more called for.


Edit Form

Comment on the page Fusion 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.
Avoid Inflammatory Comments
If you are feeling anger, keep it to yourself until you calm down. Avoid insulting, blaming, or attacking someone you are angry with. Focus criticisms on ideas rather than people, and understand that criticisms of your ideas are not personal attacks and do not justify an inflammatory response.
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.