[High] [Task] [WIP/Incomplete] DoT/debuff system defined in spire-combat-spec but "No runtime" implementation status #277
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type: Work in progress / Incomplete feature
Priority: High
spire-combat-spec.md §11 Known Gaps:
spire-combat-spec.md §6 defines a complete debuff/DoT system with:
ActiveEffectinterface withtype,remainingDuration,magnitude,source,bypassArmor,bypassBarrierapplyChanceBut the implementation status is "No runtime" — none of this is wired into the actual combat pipeline.
Recommendation: Implement the DoT/debuff runtime system as specified in spire-combat-spec §6.
ultimate truth: this should have already been implemented, but verify, and create gitea issue if it isn't
RESOLVED — Created new Gitea issue #286. The DoT/debuff system is actually fully implemented and wired into the combat pipeline, contradicting the spec.
dot-runtime.tshandles all 9 effect types and is called fromcombat-actions.ts. The spec's "Known Gaps" table needs updating.✅ RESOLVED — Created new Gitea issue #286. The DoT/debuff system is actually fully implemented and wired into the combat pipeline, contradicting the spec. dot-runtime.ts handles all 9 effect types and is called from combat-actions.ts. Updated spire-combat-spec.md Known Gaps table.