---

name: veilbreakers-balance-check description: Use when modifying game balance numbers (damage, capture rates, synergy values). Validates changes won't break the game.

VeilBreakers Balance Check

Overview

Validate balance changes BEFORE they break the game. One wrong number can ruin months of work.

When to Use

• Modifying damage formulas
• Changing capture rates
• Adjusting synergy bonuses
• Tweaking corruption effects
• Adding new abilities/skills
• Changing cooldowns

The Balance Systems

Brand Effectiveness (10 Brands)

• 2x damage to 2 brands (strong against)
• 0.5x damage to 2 brands (weak against)
• 1x damage to 6 brands (neutral)

Verify: Every brand has exactly 2 strong, 2 weak, 6 neutral.

Synergy Tiers

Verify: Bonuses stack additively, not multiplicatively.

Corruption States

Verify: Bounds are inclusive/exclusive as intended.

Ability Cooldowns

Verify: New abilities fall within range for their slot.

The Check Process

Step 1: Document the Change

CopyWhat: [Exact number change]
From: [Old value]
To: [New value]
Why: [Reasoning]

Step 2: Launch Balance Analyzer

CopyTask: Launch balance-analyzer agent with:
"Analyze balance impact of changing [X] from [old] to [new]"

Step 3: Edge Case Analysis

Calculate these scenarios:

1. Best case: Max synergy + ASCENDED + type advantage
2. Worst case: ANTI synergy + Abyssal + type disadvantage
3. Average case: NEUTRAL + Unstable + neutral type

Step 4: Check for Breaks

Step 5: Document Decision

CopyChange: [Approved / Modified / Rejected]
Final value: [number]
Reasoning: [explanation]

Quick Formulas

Damage dealt:

Copybase_damage * brand_multiplier * synergy_bonus * corruption_modifier

Capture chance:

Copybase_rate + health_modifier + corruption_modifier + method_bonus + item_bonus

Effective stats:

Copybase_stat * (1 + synergy_bonus) * corruption_modifier

Red Flags

Stop and reconsider if:

• Change is more than ±20% from current
• Multiple systems affected simultaneously
• Edge case goes beyond intended range
• You're "fixing" a perceived issue without data