Check out Symmetric Chess, our featured variant for March, 2024.

Enter Your Reply

The Comment You're Replying To
George Duke wrote on Wed, Oct 5, 2011 11:26 PM UTC:
Okay, Lobster appears here but 2-d Lobster may, or may not be defined in M&B12. The object is to run down and respond to Gilman's last comment's last paragraph at Crab. Gilman's side point, before the interesting switching cycle terminology, is about a return in 3 without compound of duals, but Lobster definition could be Alfil plus Ferz by the example. Lobster is Tusk plus Crosscoward, right? That is locatable eventually, but even the necessary Glossary, now through 'M', does not cite chapters. So, still anyone spotting them first, please say here what referenced Lobster is compound of. Somebody must know Tusk, however how many know Crosscoward? There would be many more returns-in-3 capabilities that are not compound of duals(always having one colour-switching and other not) of course, such as Lemurian Shatranj's Bent Hero and Bent Shaman. Those novelties of Joyce are weak example for this, though kind of identical to Charles', because of questionable pass-over squares but having the same navigation as that 'a1-c3-b2-a1'. ////// ____ Added 24 hrs. later, because of no intervention: Charles' last comment at Crab is excellent except for understanding the terms. As representative, please anyone besides Gilman, define move of Lobster. This 4-year-old 'M&B12', now first being commented, is suitable place to come to grips with the piece-type Lobster, because ''Crosscoward'' is also here in third paragraph under ''pieces.'' Lobster is at second paragraph before ''Notes.'' Browse throughout and back to earlier 'M&Bxx' for which two parts make up bi-compound Lobster. A very do-able task: just settle in mind what are Tusk and Crosscoward and we have Lobster. Then there would be one example for switching cycle 3, to find other piece-type instances having its similar attribute.

Edit Form

Comment on the page Man and Beast 12: Alternative Fronts

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.
Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.

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.