Check out Grant Acedrex, our featured variant for April, 2024.

Enter Your Reply

The Comment You're Replying To
George Duke wrote on Sat, Jun 26, 2010 03:33 PM UTC:
Okay, we use only Bodlaender's Forzoni text. Knight checking, as any other piece, forces King to move or someone to capture the Knight -- or otherwise void his reach (to be inclusive of cv renderings) -- but Knight cannot be the (sole crucial) final checkmater. Shak is word for Queen, Rook, or Knight attacking King. Tuk is word reserved for Bishop-check because he reaches only half the squares ever. Pawn is even more restricted, so we call it Zod. The three are just words and have the same effect except for the (any) final checkmate. If a double check occurs, there must be a hierarchy, so who actually moved last is immaterial. King cannot be checking the other King, but can disclose a check as matter of course. In Mongolian, there would presumably certainly be no retracting a Niol, and the game is drawn, though by all appearances a ''checkmate'' is occurring but for how the attacker has happened to arrive at it! If a chain of checks is broken, there can be no sustaining Shak until one recurs. Bare King, Robado, Drawn game too. [Interestingly, it is rare to be able to discover two checks at once in Cvs, possibly making triple check all together for a position; that takes exceptional oblique pieces who do not jump, like hook-mover 13th-century Gryphon and 20th-century multi-path Falcon in posited examples.]

Edit Form

Comment on the page Shatar

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