The site has moved to a new server, and there are now some issues to fix. Please report anything needing fixing with a comment to the homepage.

The Chess Variant Pages

This page is written by the game's inventor, Rich Hutnik.

Enter Your Reply

The Comment You're Replying To
Rich Hutnik wrote on 2008-09-26 UTC
Thanks for the reply here.

Pretty much, this is an earlier set of rules.  It lays out the framework for it.  It has gone through multiple revisions since it first was posted.

I will say that one would be expected to play multiple games, to determine a real winner.  A second way to do this is to have it so that you want to be on the winning side at the end of the game.  You can defect late, and still remain.  People on losing side get knocked out of the game.  Eventually you get down to two people.  I have done an analog version (boardgame) using another game besides chess, and it worked.

Being on the winning side the longest can remain a tiebreaker though. What you do want this to test is the ability for people to judge the state of the game, their team, and be able recommend competent moves.  It is something that is also mean to add intrigue to any game pretty much, as spectators watching the crowd will wonder how the crowd will function.  It is also a way to have kibitzing done as an actual game.  And this is ideally suited for a game like chess and Go (abstract strategy game, perfect information, no luck).

As more play happens, more tweaks can be made.  Consider this a germ of an idea with some development behind it.  I do see you have a concern with people being punished for defecting.  I believe it shouldn't be rewarded or punished, just rewarding the best judgment.  One could end up awarding a higher score to the player who started on the losing side.  But, I don't see where the idea is to 'come back'.  It is meant you decide to jump ship before it is too late, as it is going down.

Edit Form

Comment on the page Vox Populi Chess variant

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.