balance-check

Game balance validation compares your actual balance data and configuration values against intended GDD targets to find outliers and degenerate strategies. It works by running domain-specific calculations across combat, economy, progression, and loot workflows after edits.

You validate loot probabilities and combat balance against your GDD by reading the design document to compare actual values and behavior with expected ranges. This design-guided approach identifies progression tuning issues and economy imbalances.

Yes, you can check your game economy configuration for imbalances by running a targeted balance analysis after any balance-related edits. The system detects economy imbalances and outputs a structured report with recommended fixes and a fix-and-verify prompt.

The best way to find degenerate strategies in progression tuning is to run domain-aware balance analysis on your configuration data. This identifies broken progressions and outputs a structured report with prioritized recommendations and a fix-and-verify cycle.

Balance analysis works with either a specific data file path or just the game system name. Providing the changed file path enables targeted domain checks, while the system name generates a general balance report with outliers and fixes.

You fix and verify detected balance issues by following the structured report's prioritized recommendations and executing the fix-and-verify prompt. This cycle helps resolve loot and combat outliers while ensuring values meet intended GDD targets.