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

Enter Your Reply

The Comment You're Replying To
Nick Wolff wrote on Sat, Jun 24, 2017 04:27 AM UTC:

Hey Greg!

It could be not a matter of forcing the tournament into certain parameters, but maybe designing the parameters around the tournament.  Without taking too deep of a look into it (as it is late here too and I wish I was intoxicated), maybe adding 2 more variants to the mix.  With 11 games, everyone plays everyone once and gets one bye.  (4 rounds - 3 games/each and 2 in the last or 3 rounds - 4 games/each and 3 in the last)

Also, subtracting variants to 6 and doubling the games played (one black and one white) in each variant should yield the same amount of games played with 1 bye each if my math is correct.  (3 rounds - 2 variants/round  and 2 games/variant)

Alternatively, we can just start the tournament with Daniel in the games, as he committed previously.  He could be on a short vacation or have wrong contact info or family emergency.  I'd be upset to join a tournament and then find out that I wasn't in it, in spite of attempts to contact me.  

I know that all of this kind of trounces the intended spirit of the tournament, but these are just a few ideas that could end the suffering for you.  I'm down for whatever, but one thing that I don't feel is right is to cut someone from the tournament after giving them the green light to participate.  


Edit Form

Comment on the page Game Courier Tournament 2017

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.