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

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Fri, Jun 23, 2017 11:58 AM UTC:

Normal chess programs probably do the capture-the-rook thing because it was a simple fix to a problem with FRC and they weren't thinking in any larger context.

With FRC on Game Courier, I was concerned with consistency across different games, and not at all with how the game had been handled by other programs. Since in most Game Courier games, castling was handled as the move of a single piece to a space it actually goes to, I just extended that to work with FRC.

If there is an ambiguity, a dialog box will ask you if you are making a standard move or a castling move.  Prompting the user is not radical, as normal chess programs do this too when you move a pawn to the last rank.

Game Courier can do this too, as it commonly does for promotions. But I did write Game Courier in stages, and when I first put together a preset for FRC around 14 years ago, Game Courier didn't have all the capabilities it has now. Back then, GAME Code did not yet exist as a Turing-complete programming language, moves could be entered only by writing notation, and the commands now in use for diambiguating moves through prompts were not yet available. The early preset probably just randomized the position without enforcing any rules. When rule enforcement was finally made possible, moves were still being entered only by notation, and the mechanisms for handling mouse moves, which includes prompts for disambiguating moves, were not yet in place.


Edit Form
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.