The site has moved to a new server, and there are now some issues to fix. Please report anything needing fixing with a comment to the homepage.

This page is written by the game's inventor, Abdul-Rahman Sibahi.

The Comment You're Replying To
Jeremy Good wrote on 2007-06-15 UTC

Another variant of this game is to make both kings royal. There are several variants with non-royal extra kings and also those with extra kings that are royal. One of the consequences of a game with both kings royal is that a fork (or direct pin with kings skewered and nothing to interpose) of kings wins the game since both can't elude check in one turn. In the second version of a 10 x 8 board, making both kings royal might be an elegant way of accomodating more power to the board.

Of this variant, I'd like to pose a sort of quasiphilosophical question for Derek Nalls: Is not the 10 x 8 version with two kings more symmetrical than symmetrical variants with just one king? Because a solo king stands out as an asymmetry to the rest of the pieces on the board.

Applying the theme of symmetry one step further, one might lessen the weakening aspect of having two royal kings by applying a balanced extra move method (similar to Extra Move Chess and Balanced Marseillais Chess) whereby only one check can be delivered at the end of the turn which must also be removed by the end of the turn (as opposed to the beginning of the turn).

Added note: Of course having the royalty of a piece determined by its location is an elegant idea too. A further nuance to explore: How about a variant based on the theme that the closest piece to a given square is royal no matter what that piece is. Just a thought. Suppose the royal square was tucked away in an obscure place. A very strong piece close to the royal square would be hard to checkmate but it would also be removed from the main theater of war, with resulting creative tension...

Edit Form

Comment on the page Kings

## 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
• An URL by itself:
• A text link:

### 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.``````

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.
﻿