The Chess Variant Pages
Custom Search



Enter Your Reply

The Comment You're Replying To
George Duke wrote on 2011-02-26 UTC
Whatever the initiating reason that propelled him, there become many reasons for Betza to stay 64-bound. ''64-only'' is his artform in itself, art pour l'art. Betza never made Xiangqi variant, Shogi variant, or Hexagonal. Or did he hexagonal? Even the one Hexagonal here Betza makes 64-spaced out of respect for the venerated dying 1400-year board tradition that size. 75% of Betza cvs appear to come after year 1995, though arguably majority of his classics are among the earlier 25%. The Betzan size (of 64) is less important than the boards of any other past prolificist during their heyday. That is because after 1999, they are concept-cvs, basically clever Mutators, sometimes brilliant, Mutators like Neto's, linked at the end. Neto different-styled is content to list them extensively, whilst Betza, entertaining and deceptively guileless, obsesses to embody them one and all. That practice is carried on by others. Usually it is hard to distill a sure coherent rules-set because Betza's are deliberately multiple even exponential, suggesting hundreds of variants in the same one cv write-up. Augmented Chess article counts 560 different armies. He gets away with that rarely becoming tiresome, never expecting most to be played. (his own refrain: ''I have not played this but....'') Exceptions include Nemeroth, which so complicated points to its sole interpretable rules-set only. [ Neto's 40 Mutators taken 2 at a time legitimately belong to himself as author alone. If he had wanted to take the time, instead of this article he could have written up 1560 separate cvs in the prolificist era or the follow-up post-your-own era, Fine_Mutators_by_Neto. Neto has both more sense and more courtesy not to proceed the other way than this concise article. ]

Edit Form

Comment on the page Rectahex Chesss

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.