Check out Glinski's Hexagonal Chess, our featured variant for May, 2024.

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Sun, Dec 5, 2004 04:10 AM UTC:
In preparation for a British Chess preset, I have added some new features
to Game Courier that are now documented here. These are the path function
and the foreach-next loop. The path function returns an array of all steps
from one space to another. The foreach-next loop iterates through all the
elements of an array. Although I could do it, I don't plan to add
additional types of looping, since I don't want to provide the ability to
create infinite loops. Foreach should be sufficient for any looping needs
any preset has.

Also, I am deprecating how endif currently works. In the future, endif
will automatically close off all elseifs within the scope of the current
if, which it will also close. There will no longer be any need to use
numbers or the all keyword with endif. I could make the switch right away
if everyone wrote endifs the same way I do, but just in case anyone has
used endif arguments for shortcuts that close off multiple ifs, not just
multiple elseifs and a single if, I am allowing time for transition before
the old way of using endif breaks down. To make the transition, replace any
use of 'endif all' or 'endif #' with 'endifs' and make sure that each
'endifs' statement closes off only one 'if' statement. The 'endifs'
command works in the same way that 'endif' eventually will.

Edit Form

Comment on the page Game Courier Developer's Guide

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.