Check out Symmetric Chess, our featured variant for March, 2024.

Enter Your Reply

The Comment You're Replying To
Rich Hutnik wrote on Wed, Apr 25, 2012 12:20 AM UTC:
What I believe is an important thing to keep in mind, when looking at
solutions, is to realize that solutions don't always fit every context. 
What I wrote about here doesn't guarantee to fit everything, but I do
believe it can fit a number of places.

In regards to what is discussed here, I hope what is described can be
recognized at least as a skill players can develop and test.  This skill is
the ability to evaluate and create situations that work to their advantage.
 The pie rule approach ends up providing a means to have this happen in, in
a way that would be in control of players.

Ok, let's apply the pie rule idea I have, modified, towards your game, For
the Crown.  As it is now, players would randomize what cards they have in
the game.  How about we consider the following:  One player gives a list of
X number of cards they don't want to see used.  The other player then
comes up with the cards they want the game configured, and the other player
then picks what side they want to be.

Idea here is you end up thinning down things and try to reach a state that
is agreeable to both players to play, even if it would give one player an
advantage. 

As for said to hand the problem off to other people to solve, I believe a
solution is superior if it is fluid and adjust, rather than a fixed
solution.  In short, if the solution is a framework able to handle what
players do, it is superior.

Again, to sum up, there are often multiple solutions for play balancing. 
Here I list a number of them:
http://boardgamegeek.com/blogpost/9808/are-balanced-sides-have-same-chance-of-winning-rea

* Have players bid for sides, using the bidding as a mechanism to give the
weaker sides and advantage, or handicap the stronger side. This bidding is
a game unto itself of sorts, and challenges players to evaluate sides.
* Have players play all sides and evaluate the differences in how the sides
were played. 
* Play the game teams and use a duplicate format. In games with luck, like
cardgames like Bridge on a tournament level, to account for the inherit
unfairness of the luck, they use a duplicate format where the same
conditions pass around and players play them all and they are evaluated.
Unlike the last idea, where individuals play all sides, this is done team
style.
* Fixed handicapping of one side, by giving it less resources or time to
play, or one side to count a draw as a minor victory.
* Use the pie rule. In this option, one player configures the game
conditions and the other player(s) then pick what side they want to play.
This also provides a game of sorts, where you try to figure out what would
be fairest in set up, and then decide what is the best options.

Edit Form

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.