---
name: systems-balance
description: Use when tuning damage, health, costs, rewards, drop rates, progression curves or in-game economies. Uses models, data and playtests to keep choices meaningful and avoid dominant strategies.
---

# Systems and economy balance

Draft from the Game studio skills library by THE DREAMING JESTER. Adapt it to your game, team and engine.

## Goal

Keep choices meaningful: no option should be clearly best, and progress should feel earned at a steady, intended pace.

## Before you start

- Gather the current numbers from data, not memory, plus any telemetry on usage, win rates and time to progress.
- State the intended pace: how long to the first upgrade, the midpoint and the end.

## Process

1. Model the system in a spreadsheet or script: inputs, formulas and the resulting time-to-kill, cost-to-power or time-to-reward.
2. Define each item or ability by its role, what it excels against and its trade-off. Every option needs a weakness.
3. Look for dominant strategies: compare value per cost, per slot and per second across options.
4. Map sources and sinks for every currency and resource. Unbalanced flows inflate or starve the economy.
5. Change one variable at a time, in small steps, and record why.
6. Validate with telemetry and playtests: pick rates, completion times, deaths and quits.
7. Keep balance data in versioned files so changes can be compared and reverted.

## Quality bar

- Every option has a situation where it is the right choice.
- The model predicts the observed pace within a reasonable margin.
- Each balance change has a reason, an expected effect and a measured result.

## Output

A balance model, a change log with expected and observed effects, and updated data files.

## Avoid

- Buffing everything until nothing stands out.
- Tuning from anecdotes when data is available.
- Hiding the maths in code where designers cannot see or change it.