Check out Janggi (Korean Chess), our featured variant for December, 2024.

Enter Your Reply

The Comment You're Replying To
Jeremy Good wrote on Mon, Jun 19, 2006 09:55 PM UTC:

The Dev appears to be a lot less vulnerable than two other well known multiple occupancy pieces, Peterson's Cobra and the wall. The rule for capturing the Dev is this: 'Devs can capture devs directly. However the other pieces of the opponent can capture the dev, if all of the four squares that dev is standing on are under threat ...' In the case of the wall and Peterson's Cobra, the entire entity is destroyed if any part of it is attacked without the whole being threatened. So the Dev suffers from weaker movement ability but this is partially compensated by greater invulnerability.

David Howe has written an essay about pieces of differing size - Growing and Shrinking: Playing with the Size of Chess Pieces. The notes to that page reference a few more such pieces.

Mark Hedden should be mentioned here as having made significant contributions to this genre of variants using multiple occupancy pieces (as well as multiple occupancy squares).


Edit Form

Comment on the page Giant 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.
Avoid Inflammatory Comments
If you are feeling anger, keep it to yourself until you calm down. Avoid insulting, blaming, or attacking someone you are angry with. Focus criticisms on ideas rather than people, and understand that criticisms of your ideas are not personal attacks and do not justify an inflammatory response.
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.