balance-check

Run a balance check on your specified system or data file to scan configurations, identify outliers, and generate a structured report on combat, economy, progression, and loot imbalances.

A balance report identifies economy imbalances, dead zones, and degenerate strategies in your game data. You need one after modifying balance data to ensure fair progression across combat, economy, progression, and loot domains.

Detect economy and progression issues by loading a data file path or system name to perform domain-specific checks. The analysis reads data from design and asset directories to output a structured balance report.

Yes, you can analyze balance data across combat, economy, progression, and loot domains. The analysis applies domain-specific checks to identify over-tuned or under-tuned systems within your game design configuration.

The balance check reads data from assets/data and design/gdd directories, requiring a system name or a path to a data file. It outputs a structured balance report aligned with your game design document targets.

The balance check relies on reading existing data from assets/data and design/gdd directories, so it is limited by the accuracy of your current configurations. It identifies outliers and imbalances but requires manual implementation of the actionable recommendations.