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

Enter Your Reply

The Comment You're Replying To
David Cannon wrote on Sat, Jul 3, 2010 01:47 PM UTC:
The short answer is no. The Princess belongs to the 'slider' family and the Zealot to the 'crooked slider' family. The Lance shares membership of both families and can therefore be assimilated by members of either family - as a simple piece. But when it is part of a compound, it can be assimilated only by members of the same family. Therefore, a Princess cannot assimilate the Lance part of the Zealot to become a Queen.

You may ask why this fussy distinction. There are two reasons. The first is that I could either allow every piece to assimilate every other piece, or I would have to draw the line somewhere. The first option would create such a huge number of pieces that even I wouldn't be able to remember them all. The second option, which I chose, means that some arbitrary distinctions have to be made. I settled on confining assimilation to within 'families' - and in the case of families whose membership partially overlaps, a certain degree of subjectivity creeps in.

The second reason for this is programming. There were a number of things I would have liked to do, but the limitations of Zillions (or, rather, of my knowledge of it) forced compromises. The case you mentioned is one, although I think I would now be able to work around it if I was so inclined. I may may tweak the program that way when I get around to it.


Edit Form

Comment on the page Diamond Chess 306

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.