2.2.1

Combat Stats 2.2.1
Critical fix
Damage dealt by players (not the GM) was not being tracked at all: many Foundry/dnd5e/MidiQOL hooks only fire on the client of the user performing the action, so if that user wasn't the GM, the data never reached Combat Stats. Fixed by relaying player actions to the GM via socketlib, which is now a required module dependency (must be installed and enabled).
Tracker mode: explicit selection restored for MidiQOL
In 2.2.0, an automatic per-roll detection was attempted to determine which MidiQOL sub-mode was in use (damage applied immediately vs. applied manually), to avoid making the user choose. The detection compared the target's live HP against the HP calculated from the roll — but this is a race condition: at the moment the roll-complete event fires, the HP update may not have arrived yet, causing misclassification even with MidiQOL's auto-apply enabled.
Reverted to an explicit choice in Settings -> Combat Stats -> Tracker mode, now with three options:
D&D 5e Standard
MidiQOL — Auto apply damage
MidiQOL — Manual apply damage
The selected mode must match MidiQOL's own "Auto apply damage to target" setting exactly. As always, changing it requires a full reload (F5) — this time on every connected client, not just the GM's.
New option: chat message sender
Added the "Chat message sender (Actor ID)" setting on the main settings screen: lets you manually enter the ID of an actor who will send the end-of-combat summary card instead of the default "⚔️ Combat Stats" alias. Leaving the field empty keeps the previous behavior.
Other changes
Removed the diagnostic debug logs added during this version's troubleshooting
Updated the README with the new tracker mode table and the socketlib dependency