The Chess Variant Pages
Custom Search



Enter Your Reply

The Comment You're Replying To
Ralf Hansmann wrote on 2013-12-11 UTC
Hi there, thanks for your comments. I have now just looked at the (my/our) rules for castling as formulated at http://www.hexenspiel.de/engl/lauf.html Actually, I also find that these need improvement... What also surprised me, is that they are not consistent with the castling (Rochade) rules we formulated in German language on http://www.hexenspiel.de/lauf.html These are formulated in closest possible analogy to the real chess, which means that castling is only possible if tower and raven (king) have not been moved previously; no field between them is threatened by the other party (respectively the two other parties in the three player version), and if no field inbetween is occupied by any figure ("Es besteht für den Raben die Möglichkeit zur Rochade, d.h. zum Stellungstausch mit dem Turm innerhalb eines Zuges -- analog zum herkömmlichen Schach. Wie dort ist diese hier nur möglich, wenn der Rabe im Moment des Zuges nicht bedroht ist, wenn weder der beteiligte Turm noch der Rabe selbst sich zuvor während des Spiels bewegt haben und wenn das Feld zwischen Turm und Rabe weder bedroht noch besetzt ist.") I think it is best and I will adapt the english rules to a correct translation of my German website version of the rules and hence, to closest anology to the real chess. It is some years ago now that the rules were put online in english, and I was not alone in developing the game. So this inconsistency between the english and german formulation of rules may be due to a discussion on whether to allow castling in the three version game also in case of a threatended field inbetween tower and king to give some flights possibilities. However, I now think that the rules should be formulated in closest possible analogy to the conventional chess rules in both the two and three player version.

Edit Form

Comment on the page Witch's Chess 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.