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

Enter Your Reply

The Comment You're Replying To
Cameron Miles wrote on Sat, Aug 16, 2014 09:26 PM UTC:
Wow... sorry about this. I really should have mentioned (the last time I moved) that I was leaving for a much-anticipated 3-week vacation the very next day. While away, I did log in to G.C. every once in a while, but only for a few minutes at a time, to just move quickly in my current games so that they would all remain active. The problem was, the A.C. game never appeared on my list of current games, so I wound up not seeing what you'd written at the end of it until now (just got home earlier today, and was sifting through the "Finished Games" list when I finally found it).

Guess I ought to get back on topic now...

The vulnerability of the Wazir-Prince was something that I immediately expressed some concern over, but what worried me wasn't that it would make him too easy to attack; the issue was that he could be targetted right from move 1, leading to forced opening moves and tactics (rarely a good thing).

The new opening layout seems to have solved this problem**, however (and very nicely, I might add), which is why I'm going to have to disagree with your assessment that giving the Prince the Wazir move was seemingly a mistake. According to the introduction at the very top of the rules page, Amalgamated Chess is meant to be "a fast-paced, aggressive game". As it is now, the game accomplishes this about as well as any chess variant could ever hope to; it's about as close to pure attacking chess as you can get. Is this really "the opposite" of what you had hoped for?

Personally, the extremely sharp, dynamic, and non-materialistic nature of the gameplay is one of my favorite things about the version of A.C. we've been playing. Moreover, I think it is something that a lot, if not most, of chess variant players like to see - variants that are faster and more aggressive than FIDE chess. For this reason, I think the idea of weakening the royal pieces in this game was actually a brilliant one.

If A.C. has any shortcomings, it may be the lack of defensive resources available to its armies. Because of the way promotion works, every single piece on the board is 10 times more effective on the opponent's side of the river than on its own side. I did have an idea that may help to balance attack and defense in this game. It involves replacing the Elephants (which can be dangerous offensive pieces) with a useful defensive piece, that cannot cross the river. Because the invading pieces are so powerful (due to promotion), I would suggest making these defenders reasonably strong - perhaps the move of the "War Elephant" is a good fit.

The above proposal would give the game an additional similarity with the popular Xiangqi from the East, as well as preserve the game's ability to be played with a standard chess set. Most importantly, it would give both sides at least a sporting chance to fend off attacks, so that victory is not always guaranteed as soon as 1 or 2 pieces break through into enemy territory.

One last note: the rules page still gives the following description under "Setup": "Position the ... armies as in regular Chess." This should probably be edited, in light of the recent changes made to the initial setup.

** Admittedly, the playtesting we've done for the game's latest version has been very limited, with only one game so far from the correct starting position.

Edit Form

Comment on the page Amalgamated 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.