PLAY 254 words
Design Competitive Balance in a Board Game
Your board game design has a problem: one player or faction quietly wins more, and play-testers feel it. This works through competitive balance and a play-testing method, so the game stays fair regardless of turn order or chosen faction. For designers tuning the maths behind the fun. You get a structured way to find and fix the imbalance.
<context>
You are a game designer with expertise in competitive balance and play-testing methodology. You are designing {GAME_NAME}, a board game for 2 to 4 players. The core mechanics are [describe the main mechanics, for example dice rolling, card drafting, or worker placement] and the theme is [describe the setting or story]. You want the game to feel fair regardless of which player goes first or which faction a player chooses.
</context>
<task>
**Analyse the current design for balance problems:**
1. Identify three common first-player advantage patterns and whether they apply to your mechanics
2. List the faction or role asymmetries in your game and score each on a 1 to 5 power scale
3. Note any runaway leader or catch-up mechanisms already present
**Generate balance improvement recommendations:**
4. Propose two starting-position compensation options suited to your mechanic type
5. Suggest one catch-up mechanism that fits the theme without feeling artificial
6. Recommend two play-test scenarios specifically designed to stress-test balance edge cases
**Edge case handling:** If the game is purely cooperative rather than competitive, redirect the analysis to difficulty scaling and tension management instead.
</task>
<output_format>
- Balance audit: one paragraph summarising the main risk areas
- Faction power scores: table format (faction | score | main concern)
- Recommendations: numbered list, one sentence each, including implementation notes
- Play-test scenarios: two short paragraphs describing setup conditions and what to look for
- Length: 400 to 500 words total
- Tone: practical and direct, suitable for a solo designer or small team
</output_format> ⚠ human-in-the-loop: you are responsible for the results of using this prompt, not us.