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 Tue, Dec 15, 2020 03:12 AM UTC in reply to Fergus Duniho from Mon Dec 14 02:07 AM:

It turns out that the particular log I was analyzing may have an illegal move in it. As far as I can tell by my analysis, one player moved a previously moved Rook to his King's space, and the King was not on a space that Rook would move to while castling, though it was a space the other Rook would move to while castling. Since the other Rook was adjacent to it, moving there with it would have been a legal castling move. The result of this move was that the player captured his own King, and this caused errors down the line.

According to the comments in the game, the King's were on the d file, and the Black player was expecting the White player to make the move that appears to be illegal. White's previous move had moved the Rook to the space it would go to while castling, and Black had expected White to castle on that move. So, maybe, I deleted the wrong move from a two-move castle that was made without rule-enforcement. However, changing it to that has changed the opening position, now placing the King on the g file. This is because my code does not yet account for a King castling by moving to the Rook's space, which is how this castling move needs to be written. I will deal with that tomorrow. In the meantime, I will change it back.


Edit Form

Comment on the page Fischer Random Chess

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.