Check out Symmetric Chess, our featured variant for March, 2024.

Enter Your Reply

The Comment You're Replying To
Nicholas Kuschinski wrote on Mon, Apr 7, 2003 11:04 PM UTC:
The board is about as intuitively natural as any 43 square board could possibly be. I'm not quite sure I like the array nearly as much though: It's crowded! With so many pieces that can move so far, it seems like they need a little more space. I like the pieces though, although I think that the two step and three step aren't quite as orthogonal as the rest of them. The basilisk and the pawns in particular, are extremely interesting. Kind of wondering what a Dabbah-rider is though, I've never seen the piece before and therefore can't understand what the role of the slip-rook is. The idea of making an offset array on an offset board sounds really cool when you think about it, but now that I'm looking at it: It's ugly. The previous comment about the pawns shouldn't really be so much of a problem. On a board that has only 43 squares and 14 pawns, they take up about a third of the board at the beginning, and they become a much more generally useable piece when you get rid of all but one of them. The two-step and three-step have a range that's much less limited than it sounds, considering the size of the board, and are more useful than initial impressions might make you believe. The king, however, seems extremely weak. With so many pieces that can move so far on orthogonal lines, and with the existence of the basilisk, it seems awfully easy to checkmate him. The gun is a nice try, and is really clever, but doesn't seem to do the trick. I think it would be more interesting if he wasn't restricted to orthogonal motion, althought this might make it too hard to checkmate him, considering that the other pieces are restricted to such orthogonal movements. On the whole, its kind of hard to tell what I think of this game. I like a lot of your ideas, but they don't seem very cohesive.

Edit Form

Comment on the page Rook Mania

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.