The Chess Variant Pages
Custom Search



Enter Your Reply

The Comment You're Replying To
George Duke wrote on 2010-12-15 UTC
It's true what Shi Ji implies, that Cavebear, http://www.chessvariants.org/other.dir/abc-chess.html, should have cited Betza and Cohen's old Tutti-Frutti. Tutti-Frutti uses Cavebear's ABC template after all, and what Shi Ji says there, the Tutti-Frutti piece-types are too stong, 
http://chessvariants.org/index/displaycomment.php?commentid=26869. So Cavebear's would be a stand-alone improvement not to mention apt generalization. The first response was: http://www.chessvariants.org/index/displaycomment.php?commentid=26870. Two more points follow.  
(1) Even editors and other general prolificists get into the fashion of dismissing earlier 'identicals' saying things like ''I wasn't aware of that so it is not relevant to my 'new new new CV'.'' Crazy. Jejune. But hey the enthusiasm is there for the cover page's ''something different for a change.''  They of CVPage got that all right and then some.  This case, if Tutti-Frutti had been called to Cavebear Stroud's attention earlier, he may well have had edited-in the prior art precedent, but Cavebear hasn't been around recently. 
(2) Also relevant is that Betza for Different Armies, originally called then unequal armies, invented more or less simultaneously with Tutti-Frutti late 1970s -- with new armies added steadily til his departure in 2003  -- did not design this efficient way. Betza did define atoms in A,F,W,D and N, but those extreme elementals are too weak to total the wanted 39/31 points.  Different Armies are still being put up occasionally such as this year's Spartan Army.  Would not the best way to generate Different Army after Different Army be exactly the algorithmic A, B, C, AB, AC, BC, ABC way of instructor Cavebear pure and simple?
Http://www.chessvariants.org/index/displaycomment.php?commentid=16808,
http://www.chessvariants.org/index/displaycomment.php?commentid=25640.

Edit Form

Comment on the page Tutti-Frutti Chess 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.