The Chess Variant Pages



This page is written by both of the game's inventors, João Neto and Ralph Betza.

Enter Your Reply

The Comment You're Replying To
George Duke wrote on 2011-01-07 UTCGood ★★★★
Good concept game. The devil is in the detail. Too bad Retrochess, with each move a retraction by definition, has a lot of problems going from century-old Problem Theme to any playable CV. Not only retraction, each move by worthy rules has to be an Un-take up to a point actually, or else games go on forever. See comments in the article as well as these same ''all comments.'' Nothing would be seeming to work right all the way down the line. The best solution, not yet mentioned, is to give up on 8x8 and play them standard Los Alamos 6x6. Or at very most some deviant Congo 7x7. All dealing with is another of several hundred available Mutators, applicable to all the 4000-6000 cvs around. Still, it is good to try for 64-square embodiment, just don't publish til getting it right. After all, what involves any annotation, say hypothetical Kasparov of some hypothetical Anand-Carlsen, but ''retro-analytic,'' computer-driven post mortem, rather kin to this same thing of Betza/Neto, made into the site-compulsory cv game? The technical chess term instead refers to the constructions linked at two outside in CVPage article ''Retrograde Analysis Corner,'' not regular annotation in f.i.d.e. of course. In Betza/Neto here, how long to reach ''no legal retraction'' and the flurry of problems addressed should be soluble at once on 1950s Los Alamos; and the reverse-play of that one may even become non-trivial. Unfortunately it is dangerous rashly to get more specific generalizing the ''Retro'' class -- required Un-takes only every second or third move and all that -- to alternative cvs. The category was just fine as a problem theme all the 20th century until Betza gummed it up.

Edit Form

Comment on the page Retrochess

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.