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

Enter Your Reply

The Comment You're Replying To
Mark Thompson wrote on Sun, Oct 16, 2005 04:16 AM UTC:
The 'drowning rule' in Congo is original and interesting, but it seems to
me that it makes it awfully difficult to get an attack going. If you push a
piece into the River, your opponent has the option of immediately making a
counterattacking move that needs an immediate defensive response, which
forces you to lose the piece in the River. It almost seems as though
you're better off waiting for the other player to attack and let him be
the one whose pieces drown. Does anyone know just how the good players
avoid this problem?

Someone once observed that one of the general problems in designing a good
strategy game is figuring out how to force the players to be aggressive,
since many games tend to favor passive play unless a mechanism is
introduced to force conflict. This makes me suspect that Congo might be a
better game if the drowning rule, which seems to discourage conflict, were
revised somehow: perhaps, a piece (or at least a Pawn) should be allowed to
stay in the River one turn without drowning? Any suggestions?

Edit Form

Comment on the page Congo

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.