Chris Witham wrote on 2003-04-18 UTC
Also I think that there is a simpler way to give the rook it's move, If
the rook moves as a bishop, or as a rook followed by an optional bishop
move outward it will cover the same squares.  However it will not cover
any twice, and it will follow a path that at least somewhat resembles a
straight line.

For the bishop I think that a 3-d move followed by an optional bishop move
outward.  And of course the option to move as a bishop.  The possible
moves make the outline of a cube at any given distance from the piece,
this is good because the rook move makes the outline of an octahedron (a
cube's dual.)

This has a few advantages over the old one, first off it separates the
playing field into 6 equal parts (assuming it were in the center of an
odd-ordered board) as opposed to the old one which separated it into 14
unequal parts.  Second it is far more elegant and easy to understand than
the older version.  There were others but I’ve forgotten.

The biggest problem I see is that the new piece isn't colorbound.

Finally the Knight is missing part of it's move, it should move as shown
as well as jumping diagonally one space followed by a obligatory three
spaces in a non coplanar three squares rook like.  In three-dimensional
notation that is (1,1,3).  The extra moves return the knight to the exact
percent coverage it should have, but other pieces have more than they used
to so it is still weaker.

This changes every piece, because the queen's move is changed, and the
king's is also because now 3d moves are diagonal, so it can now move to
every space in a 3x3x3 cube around it.  The pawn can now move one space
forwards, or capture in a donut around the space it can move to.

As I said before, I think that an entire plane of pawns occupying the
second and seventh rows of each level might be a good idea.

I guess that’s it, maybe I'll send in an update.

P.S.
Thanks gnohmon I appreciate the changing to excellent.

Edit Form

Comment on the page 3D Chess, a Different Way of Looking at It

## 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:

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.

• Unordered list item
• Second unordered list item
• New unordered list
• Nested list item
• An URL by itself:

1. An ordered list item.
2. A second ordered list item with the same number.
3. A third ordered list item.

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.
﻿