The Chess Variant Pages
Custom Search



Enter Your Reply

The Comment You're Replying To
Joe Joyce wrote on 2008-04-23 UTC
HG Muller - you are not on the list of applicants. Please go to this page to register: http://chessvariants.org/index/registeruser.html

Thank you for the comment. The goal was to design a game that clearly played like chess, that had an essential 'feel' of chess, but was clearly different from FIDE. The king/'general' pieces, attacking all 8 squares around, complement the minor pieces nicely, with all attacking 8 squares unblockably. The 2 major pieces are obviously 'shatranjized' versions of the A and C. As they each attack 16 squares, double the others, but still have the same range of 2, they've made a nice fit with the basic concept. 

But this game is part of a shatranj series; thus the names. They are consistent across the series. [Heh, maybe not good names, but consistent. I admit to a naming disability. I've always thought Minister and High Priestess were good names, clearly analogous to Chancellor and Archbishop, and among my personal best efforts. Others may differ.] 

Why the bare king rule? Hubris and laziness, mostly. When the final design for this game and its sister game, Grand Shatranj, gelled, I felt it was so obvious that both games were clearly easily and readily playable as is that I posted them without first playtesting them. The bare king rule serves 2 purposes: it gives an air of shatranjness to the games, which I wanted whether or not the games deserve it; it gives me a bail-out against draws in case the games turn out to be very drawish. So far, except for Modern Shatranj, I don't think the series has had a draw, in the admittedly few games of each completed. I guess it serves mostly as window-dressing. But at high-level play, it may well diminish the number of draws. How much is another matter.

Edit Form

Comment on the page Great Shatranj page

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.