combat-system-creator

Separating combat calculation logic from state management requires a dual-system architecture that isolates pure math in a calculation system and handles state transitions in a workflow system. This approach reduces coupling and increases testability.

Adding new damage formulas and status effects without breaking combat logic requires an extensible architecture that supports new mechanics without touching core state logic. This dual-system design allows calculations and workflow phases to evolve independently.

Migrating monolithic combat code to a modular system involves splitting existing logic into calculation and workflow contracts. Migration steps guide you through separating pure math from stateful operations and integrating with an evaluation pipeline.

Yes, this combat system architecture supports phase management and status effects through its dual-system design. The CombatWorkflowSystem handles stateful phase transitions while the CombatCalculationSystem processes the associated math independently.

The best way to structure a combat system for testability is enforcing a strict separation between pure calculation logic and stateful workflow. This dual-system blueprint provides clear calculation contracts and data structures that minimize dependencies.

Damage calculations break when adding mitigation logic if calculation and stateful workflow are tightly coupled. A dual-system architecture isolates mitigation logic in pure calculation contracts, preventing new combat phases from corrupting existing state.