The Chess Variant Pages

This page is written by the game's inventor, Roberto Lavieri.

Enter Your Reply

The Comment You're Replying To
George Duke wrote on 2009-06-27 UTC
(Joyce's Philosophy should look at ''DtA'') Mark Thompson in 1996 ''Defining the Abstract'' applies to games four criteria: clarity, depth, drama, decisiveness. The same evaluative nouns could even be applied to pieces by themselves. I like Lavieri's Altair as Excellent within CVPage but would not recommend it to IAGO and Hutnik because of lack of clarity in some piece-types. Grand-Bishop moves like Bishop and also jumps like Tripper(3,3) and also has non-capturing one-step Wazir here. Like most Altair pieces, it has still additional movement along a rank and up or back three ranks with qualifications. Pretty obscure mechanics for wide acceptance, only having mind-bending depth for the fun of it. Sequential pieces have been invented and reinvented, like Joyce's Bent Hero and Bent Shaman (I rated Lemurian Shatranj high for good new combination not for re-invention) and they all have somewhat troubling clarity issues. Now Lavieri's Reducer, a one-step-delimiting Immobilizer is within this fine Altair too and is natural enough for 2-D anyway. Reducer could be among standard 25 variant pieces for IAGO. Whereas multi-path Dragon five-stepping presents lessened clarity; the full potential is already achieved by minimal-four-path Scorpion. It may be every so-called planar piece, the fad of the last week, worth considering lacks clarity, yet to be ascertained. We may never do justice to all the over 1000 piece-types in Frank Truelove's list from Pritchard, let alone Gilman's 1000 more documented. Two-path Rook being attributed to Witham in Joyce's present instigating comments is already invented long ago shows Pritchard 'ECV'. So it goes, being impossible to hold a fraction the whole field in mental sweep dispassionately. Rococo's Chameleon lacks clarity: what do to when a CV has only some one disturbing element?

Edit Form

Comment on the page Altair

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.