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

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Mon, Jan 4, 2021 09:16 PM UTC in reply to Daniel Zacharias from 05:02 PM:

Indeed, I still have to do some more work on this. The current code only works when the attacked square is at the end of the attacker's range, which is always true for leapers, and true for sliders when castling occurs on the back rank. But not when it occurs on 2nd rank.

I treat the 'passing through check' rule as e.p. capture of the King. So castling, but also sliding royals like in Caissa Brittania set an entire series of e.p. squares along their path. (Where castling is special, as even the origin is an e.p. square there.) When such e.p. squares are created by the move of a royal piece, any normal capture will also be allowed to e.p. capture (and hence make the previous move illegal in variants that have the checking rule). But this only works when sliders, which normally can only capture someting at the furthest square of their range, must test for e.p. capture on all squares en route to that too, to detect whether their path intersects the ray of e.p. squares. I did not do that yet. (So Caissa Brittania would also not work, had it been automated through the Applet.)


Edit Form

Comment on the page Play-test applet for chess variants

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.