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 Wed, Feb 26, 2003 04:06 PM UTC:
I've had an additional thought on how to make a Marseillais Chess ZRF more
optimized. Between each player's first and second move, have a dummy
player check whether either King is in check, placing a piece on a
specified location if either King is in check, and clearing the same space
if no King is in check. Then on the second move, each piece just verifies
that this space is empty before moving. This will eliminate a whole lot of
overhead caused by multiple checks of whether any King is in check.

It might also be useful to use two spaces instead of one. Checking both
spaces could be done with an or. Doing this would reduce a bit of
overhead. There could be two dummy players, a white dummy and a black
dummy. Each could first check for a marker indicating that it's side is
in check. If so, it would check whether it's still in check. If it was
empty, it would not have to check whether it's in check. In either case,
it would check whether it's side has placed the other side in check.

Another advantage of this would be the presence of visible check
indicators for each side. Zillions does not normally tell you when you're
in check. This would be a nice side effect of implementing the game in
this way.

Edit Form

Comment on the page Marseillais 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.