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

Enter Your Reply

The Comment You're Replying To
Jörg Knappen wrote on Thu, Mar 1, 2012 04:00 PM UTC:
Back to the terrain question: a promotion zone does not constitute terrain for me, also the forward direction of pawns is not dictated by terrain.

Holes in the the board are somewhat strange to Chess and may constitute terrain. Barriers of all kind are certainly terrain.

Possible terrain effect are: Difficult terrain (mountains, swamps) slowing units (pieces) down or forbidding some kind of pieces (two heavy to move there ...) on that terrain, land/water distinction (land units need boats or bridges to cross the water, water units cannot move on land (but maybe shoot units down on land), air planes can operate both on land and water, but need to land after some time and need airports or carriers for this purpose), cities (providing supplies fo any kind, generating new units, allowing of repair of damaged units).

This leads to another chess criterion

[24] A chess piece is either fully functional or captured, there is no such thing like 'damage' or 'health' with consequences to the piece (slower motion, need of repair, easier capturability). Of course, a bad position (e.g. pinned) does not count as damage. In FIDE chess the only (very mild) violation of the no damage rule is the loss of castling rights.

Edit Form

Comment on the page On Designing Good Chess Variants

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.