/godot-combat-system

Elite Combat Patterns (load on demand)

MANDATORY for combat telemetry, authoritative multiplayer damage, combo buffers, and in-game hitbox visualization. Golden path remains DamageData → HealthComponent → Hitbox.

Combo buffers

combo_system.gd — windowed StringName buffer; finishers stay normal attacks gated by combo_executed. Wire input via godot-input-handling, not _input hit logic.

Combat state gating

combat_state.gd — can_act blocks attack/dodge overlap. Prefer godot-state-machine-advanced when states multiply.

Damage popups

damage_popup.gd — pool Labels in production; this script shows the tween + crit scale pattern.

Combat telemetry

WHY batch JSON flushes: Writing every hit to disk stalls combat. Batch ~10 events then flush to user://combat_log.json.

combat_logger.gd

Authoritative networked damage

CAUTION: Clients must never apply final damage locally in competitive multiplayer.

networked_damage_manager.gd — request_damage → server validates → client_confirm_hit. Add lag-compensation / distance checks server-side.

Hitbox visualization

hitbox_visualizer.gd — toggle debug_collisions_hint; color attack vs hurt volumes differently.

Inline tutorials (moved — use scripts)

Critical hits

Roll crit on DamageData construction before take_damage — keep crit math out of UI.

func calculate_damage(base_damage: float, crit_chance: float = 0.1) -> DamageData:
	var data := DamageData.new(base_damage)
	if randf() < crit_chance:
		data.is_critical = true
		data.amount *= 2.0
	return data