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

Enter Your Reply

The Comment You're Replying To
Jeremy Lennert wrote on Sat, Apr 16, 2011 01:08 PM UTC:
If only the Basilisks complicate matters (and not the relative order of
other pieces), then at worst you need to consider every ordering of
Basilisks and decide whether each other piece is moved before, between, or
after them, which is 2 * 3^6 = 1458 combinations.  With one adjacent
Basilisk, the worst case is 2^7 = 128.  I suspect that's plenty small to
brute force.

But if you want to be clever, I believe the only times order matters are
when a Basilisk sees a pushed piece's destination before the Basilisk
moves (so it petrifies that piece only if moved second), or when it sees a
pushed piece's origin after the Basilisk moves (so it petrifies that piece
only if moved first).  So you can list all the potential interactions where
order matters:

Basilisk N relative to NW and NE
Basilisk S relative to E and W
Basilisk E or W relative to N
Basilisk SE or SW relative to S
(A Basilisk NW or SW would petrify the Go Away and prevent it from
screaming.)

Where N (north) is the average direction of the Basilisk's Knight moves;
so with a Go Away on e4, an Alabaster Basilisk on e5 is 'north' and so
order-dependent with d5 and f5, but an Obsidian Basilisk on e5 is 'south'
and so order-dependent with d4 and f4.

So the order of the Basilisk only matters relative to at most 2 other
pieces, giving at most 8 permutations in the worst case (there's only one
case where both Basilisks affect the same pieces, and in that particular
case you might as well move the Basilisks simultaneously).

Edit Form

Comment on the page Game of Nemoroth

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.