Check out Grant Acedrex, our featured variant for April, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Thu, Sep 21, 2023 09:15 AM UTC in reply to Charles Daniel from Mon Oct 22 2007 08:15 PM:

The article mentions the Flying Bomber cannot force checkmate on a bare King. I am not sure this is correct. It is true that a pure Locust (mR[cR-mW]) cannot do it, because it cannot check the corner. But it can check on the edge, (parallel to it), and the D component in the helicopeter move can check the corner. This makes all the difference:

A Bomber confines the bare King just like a Rook would, except that it leaves an escape hole at the board edge. But if the bare King would try to make use of that it would voluntarily have to move towards the edge (the attacking King chasing it to stay close), and would immediately get trapped on that edge rank or file. Like

when it was so foolish to attempt crossing the e-file (sealed by a Bomber at e1) at e8. From here you could get 1... Kd8 2. Fh7 Ke8 3. Fa7 {to get the Bomber on the safe side} Kf8 (3... Ke8? 4. Fa8#) 4. Ke6 Kg8 5. Kf6.

After 5... Kh7 we get 6. Fa8 {covers g8} Kh8 (6... Kh6 7. Fh8#) 7. Fb8 Kh7 8. Ff8 {covers h8 with the D move} Kh6 9. Fh8#. So the escape hole h7 offers no solace, but the alternative (that doesn't get you mated immediately) isn't any better: 5... Kh8 6. Kg6 Kg8 7. Fa8+ Kh8 {with a Rook this would have been checkmate, but now the corner offers shelter} 8. Ff8# {but not for long!}.


Edit Form

Comment on the page Flying Bombers Grand Chess

Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
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.