Skip to content

3.4.0

Choose a tag to compare

View all tags
@Smantella Smantella released this 21 Jul 16:53
· 1 commit to main since this release
v3.4.0
f526121
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Combat Stats v3.4.0

Requires Foundry VTT v14 and the [socketlib](https://foundryvtt.com/packages/socketlib) module.

✨ New features

🐉 Dedicated Enemies tab

The Charts window gets its own Enemies tab (shown only when "Track enemy stats" is enabled), separate from Totals — a scrollable list with a sticky header, built for campaigns with a long roster of tracked monsters.

Each row also gets a delete button for the GM: removing an enemy here only clears that entry from the Enemies tab across your fight history. It never touches player character data — damage dealt by your party stays exactly as recorded, since it's already accounted for independently on the character side.

⚠️ MidiQOL tracker mode safeguards

If your tracker mode is set to a MidiQOL option but MidiQOL isn't active, Combat Stats now tells you clearly instead of silently tracking nothing:

  • A yellow warning at world startup (GM only)
  • The MidiQOL options in the Tracker Mode dropdown are grayed out and labeled "(MidiQOL not active)" so you can't accidentally pick one that won't work
  • If your saved mode is already a MidiQOL one, a warning appears right under the dropdown in settings explaining why it's disabled

🎲 RSReforged compatibility

Combat Stats now works correctly alongside RSReforged (the maintained v14 fork of Ready Set Roll for D&D5e) under the "D&D 5e Standard" tracker mode. I've tested damage, healing, and AoE abilities (Fireball for damage, Mass Healing Word for healing) — all tracking correctly.

Note: this applies to the native tracker mode only. RSReforged itself conflicts with MidiQOL, so if you're running MidiQOL you won't be able to use RSReforged regardless of Combat Stats.

🐞 Fixes

  • Fixed a broken placeholder in two confirmation dialogs ("Delete Enemy" and "Delete Fight"): the character/fight name showed as "undefined" instead of the actual name, due to a stray {{double brace}} instead of Foundry's {single brace} placeholder syntax.
  • Fixed healing being double-counted when applied through certain roll-automation workflows (including RSReforged): dnd5e.healActor could fire twice for the same heal event, crediting it twice. Added a dedupe guard on both the acting client and the GM's side.
Assets 4
Loading