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

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Fri, Jul 20, 2012 10:49 PM UTC:
I agree with Jeremy regarding check. The paradox he mentions can be resolved by distinguishing ordinary attacks from actual attacks within the context of the game's special rules. We may say that any space attacked by an enemy piece in the ordinary way, i.e. in the way it would be attacked if this were an ordinary game of Chess, does not exist for any non-royal piece the player may move. We may assume that the effects the current player's pieces would have on the ability of the opponent's pieces to move does not recursively feed back into determining which spaces do not exist. Otherwise, we could get endless loops and paradoxes.

With regard to check, it seems we should refer to actual attacks within the context of the game, i.e. it is check when a piece actually attacks the opponent's King.

With regard to the Knight, Nightrider leaping might make more sense. In Wormhole Chess, I specifically had the Chinese Chess Horse in mind as a model for how the Knight would move. But I don't think the creator of this game did. If we think of the Knight as a simple leaper analogous to the Pawn, we may do the same thing as we would for the Pawn. When the space a Pawn might move to does not exist, it moves to the first space in its path that does. Analogously, when the space a Knight would leap to does not exist, it might leap to the first space that does exist in a Nightrider path.

Edit Form

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