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.

The Chess Variant Pages

This page is written by the game's inventor, Patrik Hedman.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on 2020-09-28 UTC

The diagram's AI uses a bit of a quirky method for detecting game end: it incrementally keeps track of a 'royalty count', where each piece type has its own 'royalty weight'. Pieces defined as royal get weight 1024, pieces defined as baring get weight 1. If the opponent's royalty count is negative after your (pseuo-legal) move, you win immediately. If not, and if your own royalty count is exactly zero, you lose. Except when the opponent is at 0 too. Then, if this was the consequence of the latest move (i.e. before the move the opponent was still positive) the game continues to check the legality of this counter-baring; otherwise it is ruled a draw.

Normally the royalty count starts at 1, so that loss of any royal makes it negative. For extinction royalty 1024 times the number of spare royals is added to the initial value. I there are any baring piece types, the initial 1 is replaced by the number of baring pieces (so that you will hit 0 when they are all gone).

You can specify which piece types should be counted for the baring, through a number of baring=N parameters. For cases like Shatranj, a short-cut baring=0 is recognized as the instruction to make all non-royal pieces baring. (Piece-type numbering starts at 1.) This system so far was able to handle all cases I encountered; in this case I defined the Rooks and Archbishops as baring, and to prevent black from losing when he loses both Rooks, I defined the King as baring as well. Then black can only lose by baring if he loses his King, but as the King is defined as royal, that would make him lose anyway.


Edit Form

Comment on the page Foolish King Chess

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.