The site has moved to a new server, and there are now some issues to fix. Please report anything needing fixing with a comment to the homepage.

The Chess Variant Pages

Enter Your Reply

The Comment You're Replying To
Anthony Viens wrote on 2018-11-14 UTC

H.G. Miller, I'm sorry, I missed your response.

Here is my problem: the move is specifically defined as 'one square orthogonally, then one square diagonally outward.'

My assumption (possibly/apparently incorrect) is that spaces without notation are not squares, do not exist, and therefore cannot be used as part of any piece's movement.

The white knight is in a8.  The only spaces that appear to be orthogonally adjacent are a6 and c8.  Diagonally outward from those spaces yields only b5 and d7.

I don't see a path to c6......without counting the quarter-circle empty space within a8 as orthogonally adjacent to a8.  Diagonally outward from that empty space yields c6 as the destination.  But I wouldn't think the empty space would be used as part of the path, at least without directly mentioning it; such as 'the knight can leap over non-existent squares.'

(If the Knight's movement was defined as one space diagonally, then one space orthogonally outward, it makes sense.  The white knight starts in a8, diagonally moves to b6 or d7, and then moves orthogonally outward to one of b5, c6, or d7.  The white knight would actually have two routes to c6.  But the movement path of the knight is specifically defined as 1 orthogonally, then 1 diagonally outward.)

Basically, Ben Good went through the trouble of specifically defining the leaping knight's move (something I consider necessary to avoid questions on this crazy cool board) and then his example does not seem to match the defined move!

If there is a path I am missing, please show me.  But the only one I see is using the non-existant quarter circle within a8.

Edit Form

Comment on the page Crazy 38's: The Knight

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.