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
George Duke wrote on 2012-04-23 UTC
Morley*. Also there can be two promotion zones, or three promotion zones. Morley was serious about the expansion of the board to 88 and entire book is devoted to it world-war-two era. I believe David Howe cites it in section of the Guide. Try optimizing the rules here given the board and the pieces. A lot of so-called new CVs are really re-designs and optimizations not deserving separate game status. Pawns reaching corner maybe should have to underpromote in Morley rather than tack-on extra rule to get the Pawn out of there, suggested by the other two comments. Then if reaching the opponent's pieces' squares instead, there is the regular Queen promotion, obviously intended by Morley. And finally third if reaching the final back-rank, some higher possibility -- like the Amazon. Amazon I just mentioned recently as way to un-deadlock the tie problem Hutnik raises in going-on thread. But suggestion of Amazon there is somewhat frivolous, for real sake of condescension to ordinary gms understanding RBN right away if little else. The best draw-buster I can think of, for conventional implementation, is control of the central four by one or the other King. Morley would rather opt for this different board outright to rejuvenize Chess. Also, Black, compare this board by chess professional to Reshevsky's ''professional'' design at Zonal. Both retain pure and simple RNBKQP with boards saw-toothed-like. Now if wanting a CV rather than a reform, call Pawn reaching the originally empty back opponent rank an alternate Win course, and forget the Amazon. ///*F.W. Morley mathematician chess-involved is father of F.V. Morley who wrote the Chess book of larger boards. The same book is recollection of F.W.M. too.

Edit Form

Comment on the page Morley's Chess

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.