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

Enter Your Reply

The Comment You're Replying To
Joe Joyce wrote on Fri, May 4, 2007 12:43 PM UTC:
Thought-provoking comment by Abdul-Rahman Sibahi. If I were to take his approach, I'd dump the row of berolinas and shorten the board to 12x12 or even 12x10, leaving 4-6 empty rows between the pawns. I think this would speed the game back up, as I think the suggested version would slow it down - you might wanna call it 'Paroxysm' in view of how you'd get the berolinas through the row of friendly pieces 2 squares in front of them... :-) Seriously, I think his suggested version would be a slower, more difficult game to play, but posing an interesting problem in development.

Consider the effects of the suggestion. First, it adds 8 more pawns to the mix, changing the pawn:piece ratio to 1:1 from 2:3. Second, it reduces the 'front' of the armies from 16 squares to 12. You get a 20% increase in total pieces and a 20% decrease in attack lanes toward the opponent. What this does is change the 'Average Friendly Pieces per File' from 3 to 4, a 33% increase. Now, the pieces are lined up 4-deep, instead of 3. All other things being equal [and they're not; the average piece speed has gone down from the introduction of the extra 8 pawns], I think that the game must be longer, less clear, and more drawish than the original, based on general principles. On the positive side, I think the suggestion allows for a game of greater depth, both tactical and strategic.

Edit Form

Comment on the page Cataclysm

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.