This is one of our Featured Games. Click the link to check out our others.

Nasmichael Farris wrote on 2005-03-06 UTC
Fergus Duniho speaks about Alice Chess and en passant. 'Jellis mentions some details about en passant that I also thought of while working on my own Zillions Rules File for Alice Chess. First is the question of whether the capturing Pawn has to be on the first or second board. As I understand en passant, it allows a Pawn to capture a Pawn it could have captured if that Pawn had made a one-step move instead of a double move. Thus, the Pawn that can take another by en passant must be the one that could have taken the Pawn if it had moved only one space. This means a Pawn on the second board. When a Pawn makes a double move, it will switch boards, and if it lands beside an enemy Pawn on the other board, that Pawn will normally be able to take it by en passant. But Alice Chess does introduce one situation in which the rule of en passant becomes ambiguous. When a Pawn makes a double move, it may pass over a space whose corresponding space on the other board is occupied. Thus, the space the enemy Pawn would have to go to for an en passant capture will be occupied.' I was reading an article from Alessandro Nizzola on 'Passar Battaglia' (http://www.chesscafe.com/text/skittles222.pdf) wherein the double move was used to pass the battle by, and in the Italian rules, the opponent could not recapture. So perhaps Alice allows conditions where en passant and passar battaglia co-exist. Does the community feel there is a need for either one or the other, or, in the spirit of Alice, that both are interwoven? Fergus' analysis is sound, but there are loopholes, not because of his argument, but because of Alice's mirror world. Discernment is tough with the board shifts, and adhering to the few extra rules brings about so many new possibilities. Arguments in either direction are possible, and perhaps that is why Parton offered up the statement on en passant, 'it is usual to forgo it.'

Edit Form

Comment on the page Alice 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
• An URL by itself:

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

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