Damage Health Framework

Overview

Complete damage and health system with interface-driven design, multiple damage types, resistance calculations, and event-driven architecture for UI/VFX integration.

When to Use

•Use when implementing health for players, enemies, or destructibles
•Use when creating damage types (Physical, Fire, Ice, etc.)
•Use when implementing resistance/vulnerability systems
•Use when building combat systems with critical hits
•Use when UI needs to react to health changes

Architecture

code

┌─────────────────────────────────────────────────────────────┐
│                      IDamageable                            │
├─────────────────────────────────────────────────────────────┤
│  TakeDamage(DamageInfo) → DamageResult                      │
│  CurrentHealth, MaxHealth, IsAlive                          │
└─────────────────────────────┬───────────────────────────────┘
                              │
           ┌──────────────────┼──────────────────┐
           ↓                  ↓                  ↓
   ┌───────────────┐  ┌───────────────┐  ┌───────────────┐
   │   Player      │  │    Enemy      │  │ Destructible  │
   │HealthComponent│  │HealthComponent│  │HealthComponent│
   └───────────────┘  └───────────────┘  └───────────────┘
           ↑
   ┌───────────────┐
   │ DamageDealer  │ ─→ Weapon, Projectile, Hazard
   └───────────────┘

Components

Component	Purpose
`IDamageable`	Interface for damageable entities
`DamageInfo`	Struct with damage details (amount, type, source)
`DamageResult`	Struct with damage outcome (dealt, blocked, killed)
`HealthComponent`	Reusable MonoBehaviour with events
`DamageDealer`	Component for damage sources

Damage Types

•Physical: Standard melee/ranged damage
•Fire/Ice/Lightning: Elemental damage
•Poison: Damage over time
•Holy/Dark: Magic types
•True: Ignores all resistances

Best Practices

•✅ Use DamageInfo struct for all damage passing
•✅ Subscribe to events for UI, VFX, audio responses
•✅ Use resistances for enemy variety
•✅ Critical hits for exciting combat
•✅ Implement IDamageable on anything destructible
•❌ NEVER modify health directly - use TakeDamage/Heal
•❌ NEVER forget to unsubscribe from events

Events

csharp

OnDamaged(DamageResult)   // After damage applied
OnHealed(float amount)     // After healing
OnHealthChanged(current, max)  // Any health change
OnDeath()                  // When health reaches zero
OnRevive()                 // When revived from death

Few-Shot Examples

Example 1: Basic Enemy Setup

User: "Create an enemy with 100 health that takes fire damage."

Agent:

csharp

// Add HealthComponent to enemy
var health = enemy.AddComponent<HealthComponent>();
// Configure in inspector: MaxHealth = 100
// Set Fire resistance to -0.5 (takes 50% extra fire damage)

Example 2: Weapon Damage

User: "Make a sword that deals 25 physical damage with 10% crit."

Agent:

csharp

var dealer = sword.AddComponent<DamageDealer>();
dealer.SetDamage(25f);
dealer.SetCritChance(0.1f);

Example 3: Health UI Integration

User: "Update health bar when player takes damage."

Agent:

csharp

healthComponent.OnHealthChanged += (current, max) => 
{
    healthBar.value = current / max;
};

Related Skills

•@status-effect-system - Poison, burn, bleed effects
•@ability-skill-system - Abilities that deal damage
•@interface-driven-development - IDamageable pattern

Template Files

•templates/IDamageable.cs.txt - Core interface + structs
•templates/HealthComponent.cs.txt - Reusable health component
•templates/DamageDealer.cs.txt - Damage source component