balance-check

Detect game balance outliers by analyzing balance data files and configuration across combat, economy, progression, and loot domains. This process identifies degenerate strategies and validates economy pacing against your intended GDD targets.

Progression tuning validation checks for broken progressions and economy imbalances by comparing configuration data against design targets. You need this validation after making balance-related changes to prevent silently introducing unfair or ineffective gameplay.

Validate loot rarity distribution by reading loot balance data from assets/data and consulting the GDD under design/gdd. The analysis checks loot configuration against intended design targets to identify imbalances and output a structured health report.

Yes, you can check combat balance for a specific system by providing an explicit system name argument or targeted file path. This domain-targeted analysis focuses outlier detection on the selected combat data rather than evaluating the entire project.

The best way to identify broken progressions is running an evidence-driven balance analysis that enumerates data sources and flags degenerate strategies. This produces a structured report with health summaries, outliers, and prioritized recommendations to guide your fixes.

Yes, game balance verification requires reading data from assets/data and design/balance directories, plus consulting the GDD under design/gdd. Without these specific folder structures, the analysis cannot access the necessary configuration and design files.