Check out Atomic Chess, our featured variant for November, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Wed, Sep 27, 2023 08:01 PM UTC in reply to Bob Greenwade from 06:42 PM:

The ipfmR part would also allow a non-capture hop over an enemy piece without capturing it. I don't know if this was your intention. If it should be friendly hopping only, you could use the kludge idaufmR, where the d limits the first leg to reaching friendly pieces only, and the u in the next leg would undo the destruction this involved by unloading that friend on the same square.

I hope to get rid of this kludge, one day. Perhaps this is already achieved, but the price is that you then have to define a captureMatrix. A ^ in that matrix outlaws hopping in a type-specific way, so that you could keep specifying the universal hop ipfmR, and then outlaw doing it over all enemy piece types, but not with friendly piece types, by writing as many ^ as there are piece types (shorthand ^N) in the row for the Helepolis, after a dot . (which would apply to hopping over an empty square, which is nonsense and so doesn't have to be outlawed).


Edit Form

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