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

Enter Your Reply

The Comment You're Replying To
LCC wrote on Sun, Dec 15, 2002 03:25 PM UTC:Excellent ★★★★★
I don't think the newcomer x veteran idea makes much sense, because it's
based on the false concept of familiarity - that veterans have extensive
knowledge of their fellows' previous submissions and that newcomers have
none. I seriously doubt it. I am a relatively new visitor to this site yet
I have checked *all* submissions to the previous contests, and playtested
some, including all previous winners. This may, of course, affect my
decisions - 'oh, this guy didn't do as well as in that other contest...
it's good but I'll send him a message by voting low' (of course, effect
exagerated) and there is no simple way to oppose this - adding me to the
list of veteran judges? On the other hand, some 'veterans' may have had
little contact with other submissions, and even forgotten who authored
what. It's doubtful they will have any more 'twisted' reactions than
newcomers.

On a more serious issue, most volunteered judges, including me, are
participants in the contest. Will judging be limited to us, or any
volunteer will be accepted? If the latter is correct, how will 'foul play'
be controlled? While I am all in favor of trusting people's gamesmanship,
the idea of ficticious judges voting alike to benefit someone isn't so
farfetched as to be dismissed.

Edit Form

Comment on the page 84 Spaces 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.