The Chess Variant Pages

This page is written by the game's inventor, Joe Joyce.

Enter Your Reply

The Comment You're Replying To
Joe Joyce wrote on 2007-07-15 UTC
Thank you for the comments, David and Jeremy. 
David, you are absolutely right in the limitation to the king, being unable to move into/through check. Thank you for making it explicit. Heh, thought you'd get me on the WW, which: 'winds up on exactly the same squares as the war elephant', which it doesn't, exactly. It misses the 4 Alfil squares. It counterbalances those 4 squares with the 4 initial wazir squares. This leads me to suggest that since both pieces hit the same number of squares and have the same range, the more powerful one is the one that attacks more close squares. This would be the double wazir [isn't there a better name for this thing? C'mon, what is it?], which, since it may change color, should be more powerful anyway. Finally, the 'and/or' in the linear H&S descriptions is my way of trying to get off cheap in explaining the exact moves of pieces that may step one, leap 2, or do both, in either order, but only in a straight line. There, I got it all in. ;-)
Jeremy, you are right about the weakness of the corner pieces. They are, in fact, my knight analogs for LemS and LemT. And you well know the Hero pieces are rook analogs that moved in 1 square and took over the knight's position, because they took over the knight's move. That's how the knight pieces got banished to the corners, which is supposed to be a no-no. But is it always? The FAD can get out of the corner easily; on turn 1 it has 2 moves, 1 of which attacks 2 of the 4 center squares. The FAD is a strong piece for a knight analog, even though it is colorbound and stuck in a corner. Is the double-wazir good enough in the corner, or will it languish like the 'woody rook' often does when it starts in a corner?

Edit Form

Comment on the page Lemurian Shatranj

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.

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.