You are on the backup site for Chessvariants.com. Any posts, moves, or other changes you make here will not be permanent, because the pages and database from the main site will be backed up here every midnight EST. Additionally, things may not be working right, because this site is also a testbed for newer system software. So, if you are not here to test, develop, or merely read this site, you may want to change .org to .com in the navigation bar and go to the main site.



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 2021-04-12 UTC

"Are those now the ‘default’ versions of the Hero and Shaman then?" - Bn Em

Actually, the bent versions were the original design for those 2 pieces. They are made as literally half of the pieces I put in Atlantean Barroom Shatranj, but are about three quarters as effective. At that point I hadn't realized the knight was unnecessary in Lemurian because the hero did the knight's job. I'd put the heroes in the rook's positions and still had the knights in their positions, but they were too weak, and I was kinda stuck. Then the Muse granted me an inspiration.

I am more wargamer than chess enthusiast, and old enough to have been there at the beginning of the wargaming hobby. One thing those early games did was compare themselves to chess, and that idea of military chess stuck in my head for decades before I took a side track by considering the limited or linear (good naming choice!) hero and shaman, and Chieftain shatranj popped into my head. Since I still hadn't gotten Lemurian right, I wrote up and posted Chieftain Chess (it sounds better than Chieftain Shatranj) before Lemurian, thus making the linear versions of hero and shaman appear to have been designed first.

So, yes, courtesy of better naming and actual precedence, the "bent" versions are the default, and the linear versions are the "derived" pieces.


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.