The Chess Variant Pages



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

Enter Your Reply

The Comment You're Replying To
Michael wrote on 2015-09-26 UTC
Thank you H. G. Muller for your input, I am always happy to receive feedback and ideas. The king double move to c2/g2 is interesting, however I feel that the king may not always be too safe on those squares, mostly due to the number and power of the bishops. e.g say the king double moves to g2, and then later the g2 and b7 bishops trade off. Now the king is rather vulnerable on g2, and whites queen does not want to get lured onto the a8/h1 diagonal, as blacks other white squared bishop might immediately spring into action.

Also I don't want to give up on Luft Castling just yet! I agree with what you said about the location of the rooks, but I have found through testing (without special castling) that the luft manoeuvre sometimes tends to happen naturally (manually). It seems to have some advantages, that would be even better if sped up. This is sheer luck, as I can now see that there was a distinct lack of sophistication in how I decided to include it as an option (i.e. "okay so let me find something that is like castling, but with an extra rook"!). It has the advantage that it immediately accelerates the development of 2 rooks, while moving the king to a safer place behind some wing pawns and the luft rook. It seems counter-intuitive, but somehow it seems to work, at least from my very limited initial tests.

I'm not discounting the double king move idea either though (I would prefer your first option - i.e. 2 steps to g2 subject to f1 OR f2 not being under attack). I feel it definitely needs to be tested along with the other ideas. And it could even be included along with luft castling and normal castling. I still have a lot of testing to do, which will be much easier when I can I find a way to modify an open source chess engine to include these features.

Edit Form

Comment on the page Latte 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.

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.