balance-check

You can validate game tuning data by running a balance check that compares tuning knobs against a GDD-defined baseline. It generates structured reports with data sources and recommended fixes for tuning teams to eliminate degenerate strategies.

Detecting degenerate strategies after adjusting progression data requires running a balance check to validate no outliers remain. The check analyzes XP curves and pricing against design targets, producing actionable reports with recommended fixes.

The best way to report balance anomalies across game design documents is to load relevant files from assets and gdd directories to generate domain-specific checks. This produces design-aligned reporting with structured outputs for fixes and re-checks.

Balance checking works with loot distribution and pricing data by applying domain-aware checks to these systems. It analyzes loot distributions and pricing against GDD targets to identify balance anomalies and generate structured outputs for fixes.

You need to run a balance check on your game data after adjusting balance-sensitive tuning values. This ensures consistent checks to maintain fair iteration by validating that no outliers remain and no degenerate strategies exist across systems.

Automated balancing for game design is limited to validating tuning knobs against a GDD-defined baseline. It requires relevant files to be loaded from assets and design directories, meaning it cannot detect anomalies in systems lacking defined baselines.