balance-check

To run a game balance check, execute the skill against your target system data to generate a structured report. It identifies outliers, degenerate strategies, and economy imbalances by reading your data files and design document.

Diagnosing loot and progression imbalances involves analyzing baseline targets and expected ranges from your design document. This process highlights health issues and outputs actionable tuning recommendations for your game systems.

Yes, checking game balance requires access to assets and data files alongside your design document. These inputs allow the system to understand expected ranges and accurately inform tuning decisions for the balance report.

Yes, a game balance report identifies degenerate strategies and economy outliers by analyzing your configuration data. It determines the balance domain from your inputs and highlights areas needing immediate tuning adjustments.

You should run a balance check after modifying any balance-related data or design. This ensures new outliers or economy imbalances are caught early and provides actionable tuning recommendations before deployment.

Supported balance domains include Combat, Economy, Progression, and Loot. The system determines the relevant domain from your user input and data files to produce targeted diagnostic reports.