The Chess Variant Pages
Custom Search

Enter Your Reply

The Comment You're Replying To
George Duke wrote on 2011-01-21 UTC
[Incidentally AltOrth Hex looks to in-slot soon closer to Time Travel than Fisher R.] That is still the wrong way about it. All the M&Bxxs need to be re-done from scratch from the ground up not the top down. There were already cries to re-name basic mono-leapers. The more piece-types get developed in Triangles, as they should, the more the cv art-designer crowd is going to use plain Triangles for clarity, not Squares or Hexagons under that and this binding and switching qualification.  From the One Chess 8x8 and the lesser age-old Xiangqi, players might be weened by consensus of approved cvs getting played. To connect with common sense, the CVPage artist should convey the triangle-CV on Triangles; then all avenues are getting explored helping the cause. No one as player is intent to dwell on Gilmanesque ''duality between Cubic and Tetrahedral boards'' or ''semi-duality on cubic boards.'' Instead, just state the Rules in plain parlance. Those other interesting topics belong with problemists, including prolificists themselves, as who we rightly bridle at one arbitrary specific rules-sets after another by seeming random selection.  By the way, where are Man&Beasts' Alquerque-board piece-types: Appearances are deceptive that they look square, and do not collapse them into treatment by Squares alone. Or, if going to use Weave and Dungeon connectivity,, any new pieces are more interesting than such generality on how, by twist or turn, this can really be diced up a certain way into something other than unique board.  Strategy and tactics are nil when, upon quick read, the boards and rules are not intuitive.  It never can get to a playing sequence and competition, simulation of Nature.  Where is even one Gilman game score? Or problem-theme Mate in Two? Compare that oversight to the Betzan thousands of scores:

Edit Form

Comment on the page Man and Beast 13: Straight and Crooked Moving page

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.

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.