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

Enter Your Reply

The Comment You're Replying To
George Duke wrote on Mon, Jan 4, 2016 04:39 PM UTC:
There are 8 piece-types, and H.G. finds five to be the same from Bodlaender's rendering of Murray and Cazaux's examination of the original text. They are King, Pawn, Crocodile, Rook, and Gryphon. <p> The other three are Giraffe, Lion and Unicorn. It certainly makes Lion a better leaper if allowing (3,1) camel added to (3,0). And Giraffe is about the same value whether leaper of (2,3) zebra instead of (1,4). Some confusion comes about in mediaeval texts regarding whether the starting square counts in move descriptions. Murray points that out himself, and here that's how we may get 2,3 instead of 1,4 under further scrutiny. <p> Something remarkable comes about from Muller's speculation that probably Gryphon is meant to be permitted the Ferz stop. It does make sense as the basic mode of movement of Gryphon because otherwise it could be blocked there. In other words, Gryphon can either capture or be blocked at Ferz spot, and capturing is the better and simpler mode, or then too being allowed to stop there in one-step when the square is vacant -- if no old writing contradicts it. <p> Then towards the remarkable re-interpretation, there is the Unicorn/Rhino as making Knight leap not on first move but in first leg of any move! By the same logic as Gryphon stopping at Ferz square, this Unicron/Rhino can stop at Knight square. So in fact in Grande Acedrez we have Rook, Knight and Bishop! Bishop is Crocodile, Unicorn is Knight (+ optional one-directional diagonal continuation), and perennial Rook orthogonally, giving the 3 themselves RNB 200 years before the now primitive OrthoChess 64 is born. And it fits the Stanley Random, of all things, reduction of Chess from larger ancient form.

Edit Form

Comment on the page Grande Acedrex

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.