Check out Janggi (Korean Chess), our featured variant for December, 2024.

Enter Your Reply

The Comment You're Replying To
David Paulowich wrote on Wed, Mar 30, 2005 11:55 PM UTC:

(loss-condition (White Black) (pieces-remaining 1) ) ; This 'bare king rule' creates problems for Zillions in Shatranj and other chess games. Here is an example with 5 pieces set up on an empty board:

VariantName=Shatranj (White Shah c1) (White Rukh b2) (White Baidaq h2) (Black Shah a1) (Black Rukh b8)

diagram 

1. Shah c1 - c2 [a deliberate blunder in order to test Zillions]
1. Rukh b8 - c8
2. Shah c2 - b3
2. Rukh c8 - b8
3. Shah b3 - c2
3. Rukh b8 - c8

Apparently Zillions was worried about the sequence 1... Rukh x Rukh check 2. King x Rukh 'bare king victory'. I have not seen Zillions actually play an illegal move, but this example does show Zillions failing to win a game because it reacts to the apparent threat of a future illegal move. Another Problem: every Shatranj related ZRF that I have tested will record a 'bare king victory' without granting the player the opportunity for a final move resulting in a 'two bare kings draw'.


Edit Form

Comment on the page Shatranj

Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
Avoid Inflammatory Comments
If you are feeling anger, keep it to yourself until you calm down. Avoid insulting, blaming, or attacking someone you are angry with. Focus criticisms on ideas rather than people, and understand that criticisms of your ideas are not personal attacks and do not justify an inflammatory response.
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.