The Chess Variant Pages
Custom Search



Enter Your Reply

The Comment You're Replying To
Kevin Pacey wrote on 2018-12-19 UTC

Thanks Ben. Somehow I thought I made a point of being careful whenever entering the board size parameters for e.g. a preset page, but maybe I was in a rush?!

Regarding Aurelian's question, Greg answered it earlier for me (in the Champagne Chess preset comment thread). He also suggested having rules on my preset index pages for the 9 recent presets I submitted that were accepted by an editor. I can only think for now of repeating my reply to Greg (in the Champagne Chess preset comment thread), in case you missed it:

Kevin Pacey wrote on 2018-12-03 EST

Hi Greg

I'm not sure of the details, but I seem to remember long ago Fergus instructed me to the effect of trying to keep an index page for a preset fairly clean, such as free of rules descriptions, as he felt such a page was meant to be simply a gateway to the actual preset itself.  Thus, that's why I've tried to do it that way since then.

[edit: P.S.: Fergus wrote on 2016-12-07 EST: "You don't need to explain all the rules on this {index} page {for my old Carrousel Chess preset}. This is just a jumping off page for a Game Courier preset. The appropriate place for the rules is the rules page, which you can link to from here, and the preset itself."]

Before I've almost always first made a rules page for a given game I've invented, with Introduction, Setup, Pieces, Rules, Notes sections given, as is customary for such pages, and people could read these (besides looking at the actual preset). This time I meant to get a whole bunch of games out there without taking much longer than I already had, as a lot of the games were revived ideas of long ago. It also can pay to use a name for a game before someone else might take it, as I discovered recently. I may get around to doing rules pages for some or all of my 9 recently released presets, but it could take a while.


Edit Form

Comment on the page Compound Chess page

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.

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.