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

Enter Your Reply

The Comment You're Replying To
Ralph wrote on Wed, Jun 23, 2004 10:08 AM UTC:
Isn't it accepted that in a good variant it is desirable to keep as close
as possible to ortho rules?!  Yet the Circular Society rules disallow en
passant and castling.   (Why are these differences necessary?  In
Pritard's Encyclopedia, he describes modern form of Byzantine chess:
'In
the modern game, castling K-side is permitted and pawns have an initial
two-cell move option [e.p. possible].'  From the Society's write-up of
the invention of rules by Dave Reynolds:  'Dave was an enthusiastic, if
rudimentary chess player. Such deviousness as castling and en passent met
with a furrowed brow and a shake of the head.')

Sorry to jump on this, but is that really a good basis for forming a
variant's rules, basing them on the predjudices of a beginner player?!  

Something else I don't get ...  How is the board set-up derived from a
square board ortho array?  (Everytime I cut a board in half and fold
around, the White King and Queen end up opposite than depicted in the
Society's array, or the Pawn rows end up on the inside not the outside. 
Can someone PLEASE give me precise instructions as to how to cut and fold
the board so the array ends up like the Society's array?  Thank you!)

-Ralph Peters

Edit Form

Comment on the page Circular Chess

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.