3.4.1
Combat Stats v3.4.1
🐞 Fixes
-
Fixed a crash when a fight ends or an enemy dies, on setups where
crypto.randomUUID()isn't available. This API only works in "secure contexts" (HTTPS, orlocalhost) — it silently throws on plain HTTP connections over a LAN, which is common if you're running Foundry behind a reverse proxy that only terminates SSL for external traffic, self-hosting with a container (e.g. Felddy's Docker image), or connecting through a dedicated client like FLC. Symptoms:crypto.randomUUID is not a functionin the console right when a monster is defeated or a combat is deleted, and the fight isn't tracked/saved.Combat Stats no longer depends on this API at all — it now uses Foundry's own
foundry.utils.randomID(), which works identically regardless of how you connect.
No other changes in this release.