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:
Use an explicitly scoped InjuryTracker instance per
player/character instead of relying on this shared module singleton. This
export is retained temporarily for backward compatibility with existing
consumers importing injuryTracker from systems/bodypart and will be
removed in a future major release.
Legacy module-level injury tracker singleton.
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:
Use an explicitly scoped InjuryTracker instance per player/character instead of relying on this shared module singleton. This export is retained temporarily for backward compatibility with existing consumers importing
injuryTrackerfromsystems/bodypartand will be removed in a future major release.