Check out Symmetric Chess, our featured variant for March, 2024.

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Wed, Apr 15, 2020 03:54 PM UTC:

In the same place was described a piece called the Unicorn, moving as Knight then Bishop. Supposedly the Unicorn couldn't make a capture using its Knight move, but I'll ignore that silly rule.

Not described there is a piece which makes a one step Rook move and then continues outwards as a Bishop. For lack of a name, I'll call it the Aanca (13th century Spanish for "Gryphon"). Although the Aanca is not described, one can suppose that the same mind who conceived the Gryphon and the Unicorn probably also considered the Aanca.

I don't know if Betza ever visualized movement diagrams for these pieces. Assuming non-overlapping paths of movement, the Unicorn covers most of the same spaces as what he calls an Aanca. One of the main differences between them is that the Unicorn cannot attack any of the same spaces as a Gryphon, whereas the Aanca and the Gryphon can both attack the same spaces as a Knight. This would have been an intelligent design choice, and not a silly rule, for the following reasons:

  • It makes the Gryphon and the Unicorn complementary like the Rook and Bishop are.
  • It gives the Unicorn greater mobility in tight spots, which could increase it's usefulness in the midgame.
  • It leaves the piece vulnerable to the Knight and keeps it from forking pieces like a Knight.

So, it seems likely that the designer did consider the "Aanca" and for the reasons I gave, rejected it in favor of the Unicorn.

Likewise, the Gryphon and what might be called the Hippogriff cover nearly the same spaces under the assumption of no overlapping paths. So that paths don't overlap, its orthogonal move could continue only in the direction of the longer part of the Knight leap. Like the Unicorn, the Hippogriff would have more mobility in tight spots, and its short-range attacking power would be crippled. If it were allowed overlapping paths, it would be a monster piece that could force checkmate against a long King, because it could attack adjacent ranks or files.


Edit Form

Comment on the page Bent Riders

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.