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

Enter Your Reply

The Comment You're Replying To
Joe Joyce wrote on Sat, Sep 1, 2007 05:01 PM UTC:
Ah, Jeremy, I was away when the time was extended. Now I have a chance to expand a bit on the contest idea.
Gary, great to have you back. Been agreeing with everyone, got nobody to argue with, so thanks! ;-) Great line you posted!
'With enough constraints, a design no longer is a design, but a mandate.'
My counterargument could be that without constraints, there is no design, only chaos, but instead I'll just lay out boundaries to the idea, and we'll see if they're tight enough to give all the designs a coherent theme, but loose enough to prevent everyone from being forced to design the same game [like we don't design the same games over and over again without anyone forcing us to... :-) ] 
The contest is to design a sufficiently chesslike variant that it could be 'the next FIDE chess'. Examples of reasonable contenders in this category would be Fisher Random, Carrera/Capablanca Random, Grand Chess and Falcon Chess; shogi, shatranj, large variants, multi-movers and such are not.
Specific constraints that could be decided: 
* board size - 8x8, 8x10 and 10x10, or only 10x10? 
* must all the FIDE pieces be maintained totally intact? 
* is there a minimum and maximum number of pieces? Of pawns?
I think this would provide a reasonable balance between freedom and constraint.

Edit Form

Comment on the page 2007-2008 Chess Variants Design Contest

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.