You are on the backup site for Chessvariants.com. Any posts, moves, or other changes you make here will not be permanent, because the pages and database from the main site will be backed up here every midnight EST. Additionally, things may not be working right, because this site is also a testbed for newer system software. So, if you are not here to test, develop, or merely read this site, you may want to change .org to .com in the navigation bar and go to the main site.



The Chess Variant Pages



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

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on 2015-09-25 UTC
I think both proposed methods of 3-piece castling miss the most important point of this array: the natural places to hide the King are not b1/g1, but b2/g2. The King not protecting the Pawn shield tremendously weakens the King fortress, and on b1/g1 it would furthermore be susceptile to diagonal attacks through the center.

Castling in orthodox Chess was invented to solve the problem of the Rook getting trapped by King and Pawns in the shield. This array (which is almost Makruk-like) does not have that problem at all. The King could move to b2/g2 without a worry, and leave the Rooks to roam the 1st rank.

So if an extra King double-move would be needed here to speed up development, it would be much more logical to make that a one-time sideway Knight jump, as in Chaturanga or Cambodian Chess (Ouk). That would put the King directly on g2. Note that a Rook on the f-file is not necessarily better than on the g-file; usually it has to be moved after that. Conventional castling only served to prevent its trapping, it doesn't really develop it.

You could make a King double move to c2/g2 subject to the squares d1 or f1 not being under attack, or perhaps f1 and f2 (or c1 and c2) not being both under attack, apart from the usual conditions of not being in check and not having moved before.

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.