Check out Symmetric Chess, our featured variant for March, 2024.

Enter Your Reply

The Comment You're Replying To
Antoine Fourrière wrote on Thu, Nov 11, 2004 05:44 AM UTC:
Thanks again for the congratulations, Roberto, but there is little doubt
that having one hour for each move reflected in the outcome, especially
when I ended up sacrificing my Rook in our game of Anti-King Chess. Most
participants (and non-participants) had several other things to do, such
as work, family, studying or maintaining this site. 
In my view, the only fair equalizing methods are
1) to give all players enough time to think between each move, that is,
allowing them a pace of only one move per week at times in a given game.
For next year, I would suggest a January to June round-robin of six or
eight games, and a seven-player September to November final of six games
because these seven players might have enough time. (I would also allow
two players to replace their assigned game with any game that has been
played in any yearly tournament such as this one or last year's
tournament.) And I think you need a more lenient pace at the beginning of
the games, not merely to avoid blunders, but also to assess the possible
strategies, and because after twenty moves, half the games are already
more or less decided and you can drop them anyway if you're losing.
2) to play each game in four hours, or by slices of ten moves by hour with
one player playing a secret move at the end of the slice, like in
FIDE-Chess. Of course you need to have both players connected at the same
time (probably feasible on Saturdays and Sundays), but there is also the
problem of your Internet connection. It is one thing to lose an
independent game because of a technical problem, but I wouldn't like to
lose a Tournament that way. (Now, the penalty for not playing within the
clock in the middle of a ten-move slice in a given game could be the piece
of your choice (unless your opponent doesn't want it) the first time, that
same piece to drop for your opponent the second time and loss of the match
the third time. But it sounds overly complicated.)
Nevertheless, the implementation of that kind of device might be useful.

Edit Form

Comment on the page Game Courier Tournament #1

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.