Check out Atomic Chess, our featured variant for November, 2024.

Enter Your Reply

The Comment You're Replying To
Rich Hutnik wrote on Mon, Apr 7, 2008 08:23 PM UTC:
There is a separate entry, on here, that looks at the way can be unbounded, and could produce an infinite number of variants, based on a change in how he rules are set up. I will have to ask whether or not turn-order is finite or infinite. It might be show that a player moving N moves in a row, could always win a game. This would then put a natural boundary, and would not be infinite. You can find that thread here: http://www.chessvariants.org/index/listcomments.php?subjectid=UnboundChessList This then points to the Chess of Tomorrow Project Wiki site entry here: http://chessvariants.wikidot.com/forum/t-51667/chess-of-tomorrow-project-who-is-interested#post-140383 So, the idea of this part of the Chess of Tomorrow Project is to look at what elements of chess would be able to produce a Calvinball (never play with the same rules twice) Chess, verses being finite. I welcome any other people to contribute here to input into this and see what may or may not fit. The Wikidot entry would be appropriate place to go.

Edit Form

Comment on the page IAGO Chess System

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.
Avoid Inflammatory Comments
If you are feeling anger, keep it to yourself until you calm down. Avoid insulting, blaming, or attacking someone you are angry with. Focus criticisms on ideas rather than people, and understand that criticisms of your ideas are not personal attacks and do not justify an inflammatory response.
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.