Warning: This singleton does not track any playerId/character identifier
on injuries. All recorded injuries are stored together in a single collection.
For any scenario with more than one character (including 1v1 combat), you
must create a separate InjuryTracker instance per character to avoid
mixing injuries between characters:
This singleton is intended only for simple, single-character use cases
(e.g., local visualization tools, single dummy target, or non-combat demos)
where all injuries belong to one entity.
Use per-character InjuryTracker instances instead to avoid
mixing injuries from multiple characters.
Singleton instance of Injury Tracker.
Korean: 부상 추적 시스템 싱글톤
Warning: This singleton does not track any playerId/character identifier on injuries. All recorded injuries are stored together in a single collection.
For any scenario with more than one character (including 1v1 combat), you must create a separate InjuryTracker instance per character to avoid mixing injuries between characters:
This singleton is intended only for simple, single-character use cases (e.g., local visualization tools, single dummy target, or non-combat demos) where all injuries belong to one entity.
Use per-character InjuryTracker instances instead to avoid mixing injuries from multiple characters.