Check out Janggi (Korean Chess), our featured variant for December, 2024.

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Thu, Oct 16, 2008 01:18 AM UTC:
I rewrote part of Game Courier to clearly distinguish between user input and programming code, so that I could write code that restricts user input without affecting any programming code. One consequence of this is that notation no longer works as programming code unless it is preceded by the keyword 'MOVE:'. I could fix it so that notation can be used as programming code again, but it would involve duplicating code, and I would rather encourage the use of commands for programming code. The operation you are using @- for can be done with the empty command. Just replace your two lines with the statement 'empty e5 f5;'. The statement 'capture e5 f5;' will do the same thing but keep track of the last piece captured, just as if you used notation. But given your reason for this code, what you're really trying to do is modify the value of the $piecekeys variable, which can be done with the setsystem command. Use this statement for that purpose: 'setsystem piecekeys c C f F k K n N p P r R s S 1e 1E .1ef .1EF;' This will let your setup be accurate while still including the extra pieces among the available pieces.

Edit Form

Comment on the page Game Courier Logs

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.
Avoid Inflammatory Comments
If you are feeling anger, keep it to yourself until you calm down. Avoid insulting, blaming, or attacking someone you are angry with. Focus criticisms on ideas rather than people, and understand that criticisms of your ideas are not personal attacks and do not justify an inflammatory response.
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.