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

Enter Your Reply

The Comment You're Replying To
David Paulowich wrote on Wed, May 23, 2007 06:37 PM UTC:

Incidentally, the 'wraparound' coordinates [zabcdefghi] and [0123456789] are something Ralph Betza and I used years ago in email discussions of 10x10 variants, especially those that placed White Queen (d1) and King (e1). To help clarify my intentions for Jumping Knights Chess, I have decided to include a version of Peter's statement: 'Note that Pawns on edge squares are trapped unless a capturing move presents itself, and Rooks on corners are similarly trapped, since in both cases the piece's noncapturing move would land on an edge square, which is ... only allowed on a capturing move.'

Peter has also written: 'These edge squares can only be entered as the result of a capturing jump, and pieces sitting on them are obliged to capture if possible.' and 'Only a capturing move may end on one of the 36 edge squares. A player with a piece on an edge square that has a possible capture (even a pawn with an en-passant capture), must make that capture, even if it results in their King being captured.' Time to take a deep breath. We seem to be diverging at this point. A literal interpretation of his set of rules leads to the conclusion that, for example, a Rook on a corner square must capture an opponent's piece on the edge of the board. My [Rule 4] only applies to a piece that '... has a legal capture that takes it off the edge of the board ...'


Edit Form

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