The Chess Variant Pages
Custom Search



Enter Your Reply

The Comment You're Replying To
George Duke wrote on 2011-01-27 UTC
How many of the 21 Man & Beasts have you learned well? 1? 10? All 20? No easy answers? Start with M&B03 here, the easiest. A piece moves, and there is a leap length. Now which of the compounds of Duals, always bi-compounds, deliver Mate with King alone? (not addressed much by Gilman's anti-problemist bent, let's say) Gilman notwithstanding, sufficient mating material is standard Chess criterion to separate major/minor piece-types, right? Answer: only the first two, Man(W+F) and Gnu(N+Camel), as experimenting on board shows. The formula algebraically is two times the sum of SOLLs, to find the other one that matches for each compound. If already lost, read the article and other comments. By the third one and outward the fourth, fifth, the piece-type does not achieve it. So only the first two compounds of Duals deliver mate. That means all the other compoundings of Duals are rather weak units made as they are of two long-range leapers, known to be low piece-value. All that seems to recommend them then after those first two Dual-compounds is that they triangulate. Triangulate of course is to return in three, the way Queen or King do. Now other paired leapers, for example (Dabbabah + Camel), triangulate without being Duals; so triangulating is not really all that unique. Bi-compound duals are okay as mnemonic and organizing thought as far as that goes, but not great use to put into CVs once at and beyond Camel and Zebra distances. They are essential mostly for nomenclature. For follow-up, does Gilman really stress duals in his 200 CVs? Or mostly just in the Man & Beasts? Rather than compounds of duals, I think Gilman and other designers implement long-range component with short-range atom N,F,W,D, or A. That creates a piece-type of more useful point value 3.5 to 6.0.

Edit Form

Comment on the page Man and Beast 03: From Ungulates Outward 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.