Check out Grant Acedrex, our featured variant for April, 2024.

Enter Your Reply

The Comment You're Replying To
George Duke wrote on Mon, Apr 12, 2004 04:03 PM UTC:
Coined in 2003 by Ralph Betza (and never used by anyone else)the term 'Lame' is applied to 
Dabbaba, where from e4 it can move to e6 if and only if e5 is empty. 'Lameness' to him makes a 
leaper not a leaper, since it requires unobstructed pathway.
Yet Falcon uniquely has three(3)pathways to each square 3 steps away not reachable by Knight 
or Queen. So neither lameness nor leaping describe Falcon. Aronson goes on: 'One result is that, 
unlike with Lame pieces, if Black's Falcon attacks White's Falcon, White's Falcon also attacks 
Black's Falcon.' [Later I delete here some lines speculating what a 'lame Bison'is. 
Who knows? Aronson refuses to define it; as of April 2004, no one has 
used 'lame' for any oblique mover at all. The uncomplimentary term originates with Aronson. 
He just wants pejorative adjective attached to Falcon, and succeeds to the extent  
others now start calling F 'lame'--after Aronson writes that Falcon is not lame.  
Altogether a worthless, deliberately misleading move description.]
It is not worth delving into these 20-Questions-like what-it-is-not
snapshots of F move.  Just go to original articles, where Falcon defined affirmatively
in terms of Rook, Knight, and Bishop, and those four standards' mutuality
and accompaniments are honestly and systematically related.

Edit Form

Comment on the page Horus

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.