The Chess Variant Pages

Check out Marseillais Chess, our featured variant for February, 2024.

Enter Your Reply

The Comment You're Replying To
james spratt wrote on Sun, Oct 14, 2007 04:41 AM UTC:
Hi Jonathan, Hi Graeme: Jonathan, you're probably right about leaving the rules alone (until I've tried it the other way--Bishops colorbound, Knights orthogonal (wall) departure only, and Pawns no side-stepping toward home row) because it works pretty well as is, and it's been posted long enough that many people have probably already tried it and hopefully, liked it the way it is. Have you played it? For anyone who'd like to try it, fabricating a board out of posterboard requires but little geometry, and finding pieces just means buying two normal chess-sets and spray-painting one team of 16 an odd color, and you're ready to go.

Graeme, you're 'way ahead of me on trigonal moves for faerie pieces, so I'll take your word for it. I noticed your Delta 88 Bishop move rule differs from mine, then figured maybe the shape of your board (I wanted to fill in the sides to make a perfect 100, then noticed that there're 44 pieces, 2 players, silly me) has something to do with it.

How pieces move on a board with triangular cells can vary considerably, obviously, depending on the shape of the board, and anyone making up his own variant, I'd say, has the right to dictate how the pieces move for his game, even though it's sensible to stick to the moves generally accepted for that piece in other games.

Are we all in agreement that 'orthogonal' means leaving the cell at more or less right angles to a wall of the cell, and that 'diagonal' means leaving through a corner of the cell? I think they're useful terms to use because they're easily recognized and universal to all shapes of angular cells. (Am I asking that everyone grasps that hitting your thumb with a hammer hurts? Duh..:-))

Edit Form

Comment on the page Chess for Three

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.