Combat Stats 4.0.0
Headline: v13 and v14 in one codebase
Combat Stats now supports both Foundry VTT v13 and v14 from a single module; no more separate downloads or duplicate maintenance. Same features, same data format, on both versions.
compatibility.minimum is now "13" (was "14"). If you're on v13, just install this version instead of the old dedicated one.
New: manual attribution for unrecognized summons
Some third-party automation modules (e.g. CPR/Cauldron of Plentiful Resources) spawn NPC actors without going through dnd5e's native Summon activity and without assigning ownership to a player — which meant their damage silently landed in the "Enemies" bucket instead of being credited to the summoner.
New opt-in setting, "Ask who a summon belongs to" (off by default): when an unrecognized NPC shows up mid-combat, the GM gets a one-time, non-blocking prompt to assign it to a player character. Nothing is blocked while you decide — damage keeps being tracked normally, and answering the prompt retroactively moves anything already accumulated to the right character.
This is on top of the existing automatic attribution, which still covers native dnd5e Summon activities, Wild Shape/Polymorph, and (opt-in) player-owned NPCs — no setting needed for those.
Fixed
- Damage taken doubled in MidiQOL auto-apply mode. A leftover code path meant to support manual-apply MidiQOL stayed active in automatic mode too, crediting the same hit twice. Damage dealt was never affected — only damage taken. Confirmed fixed on both v13 and v14.
- Accidental "Clear all history" via ambiguous trash icon. The "delete everything" button used the same icon as "delete this fight" and "delete this enemy," with only a tooltip telling them apart — easy to misclick. It now has a distinct icon/label, a confirmation message that states exactly how many fights will be deleted, and a 60-second undo window after confirming.
- Excel export notification showing "undefined." A
{{double-brace}}placeholder (wrong syntax for this module's localization calls) meant the exported filename never actually got inserted into the success message.
Notes
- No changes to the data format — existing combat history carries over cleanly on update, on both v13 and v14.
- The "Ask who a summon belongs to" prompt only fires for NPCs that can't already be resolved automatically — regular monsters dragged onto the scene as normal encounters won't trigger it unless they're genuinely unrecognized.