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

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Thu, Sep 14, 2023 02:37 PM UTC in reply to Piotr Smagacz from 01:23 PM:

I like the idea of using the Horse as carrier for Pawns or Kings. But the current rules seem a bit messy to me. For instance, the moves are not always reversible: a Pawn can step out of the Knight in any of the 8 directions, but it can only step back into the resulting Horse for one of those.

The text does not exclude that the carried piece could make a capture when separating from the (Royal) Knight, so I assume this is possible. I wonder if this doesn't make the Knight too powerful, because it basically becomes a Centaur (KN), with the quirk that if it captures through a K move you cannot reacapture it, but at most the Pawn, while the Horse is invulnerable  and can easily recharge to become another Centaur. This is almost as good as having rifle capture to adjacent squares. And that you can do it even after your move as an extra makes it similar to burning (like Odin's Forest Ox).

What happens if a Pawn ends up on last rank when leaving the Knight? Does it promote?

It also seems very hard to checkmate a Royal Knight, if it can make the royal piece to such a large number of targets (every square in a 7x7 area except the corners).

I would do away with the separating after the move. And perhaps limit the separating moves to non-captures.


Edit Form

Comment on the page Trojan 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.