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

Enter Your Reply

The Comment You're Replying To
Greg Strong wrote on Wed, Jul 1, 2020 10:34 PM UTC:

1) What is the advantage of allowing a capture on a brouhaha square? Spontaneously, I find this strange: I understood that such a square hosts a piece until it is activated and enter into play, then the square disapears. Then, this square is not part of the play area really. So, I wouldn't have allowed a capture on it at all. Maybe there is something I don't see.

Good question.  The thought was that if we do not allow a capture on those squares, a piece can stay safe there potentially forever.  I do not like the idea of a piece that cannot be attacked but can still "spring into action" at any time.  The idea of this game is to add another knight-value piece and another rook-value piece to the normal 8x8 board.  The launch squares are just a new way to give some flexibility about how to develop them.

2) Why this name of "brouhaha" square? At least in French a brouhaha is a surrounding noise. Those squares are more like a fog, brouillard in French. Brouhaha/brouillard, is there a linguistic confusion there? 

In English, Brouhaha means a chaotic fight with lots of participants.  It was only the name of the game.  The squares just came to be called Brouhaha squares because of their origin, but it was not intentional.  I think Aurelian is the one who started calling them that when he used the idea in his Apothecary games.


Edit Form

Comment on the page Brouhaha

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.