Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×

[Script, Update] Aura/Tint HealthColors API

1792898563

Edited 1792898832
MidNiteShadow7
Pro
API Scripter
The Aura/Tint HealthColors API version 2 has been updated and is available in the OneClick Installer. [2.2.0] – 2026-06-29 ·   Milestone Added Death Save Integration   (Optional) — an off-by-default feature that distinguishes   dying   (configurable marker, default   skull ),   stable   (green marker, 3 successes), and   dead   (Red X, 3 failures) for player characters at 0 HP. NPCs are unaffected and keep the standard dead Red X. Automatic death-save tracking for supported sheets, so a checked or updated death-save value updates the token marker without any macro or manual refresh. Death Save Integration now appears in both the interactive   !aura   GM menu and the read-only   !aura settings   snapshot, with   !aura deathsaves   commands for enabling, watching, and configuring markers. Marker validation now warns the GM when the configured dying or stable marker tag does not exist in the current campaign. Fixed Upgrading from the interim PC dying marker build now preserves existing dying-marker settings.
The Aura/Tint HealthColors API version 2 has been updated and is available in the OneClick Installer. [2.2.1] – 2026-07-03 Added Added   !aura deathsaves sync   to force an immediate death-save marker reconciliation for selected PCs after imports, sheet changes, or missed updates. Added a one-time GM warning when a watched PC's death saves are not stored as legacy attributes. This calls out the Experimental (Jumpgate) sandbox requirement for live Beacon/D&D 2024 death-save reads and explains the failure mode on the Default sandbox. Expanded   !aura deathsaves debug   so it now reports resolved watched-field values, sheet-item API availability, the selected character's legacy-attribute count, how many watched fields are stored as legacy attributes, and a Beacon/sandbox compatibility warning when none are. Documented the Experimental (Jumpgate) sandbox requirement for Beacon/D&D 2024 death-save syncing in the README, including the known silently-reverting Roll20 dropdown issue. Changed Refined the Death Save Integration introduced in 2.2.0 so watch, sync, and debug flows now use alias-aware field resolution ( succ / success ,   fail / failure ) before evaluating marker state, improving compatibility across sheet variants without changing the GM-facing configuration model. Added a lightweight 3-second polling pass for downed PCs so death-save markers stay current even on sheets that do not emit usable legacy   change:attribute   events. Updated the fallback resolver to prefer Jumpgate   getSheetItem   reads for non-legacy death-save fields, while retaining the chat-parser probe only as a legacy-sandbox fallback. Fixed Fixed D&D 2024 / Beacon death-save syncing when equivalent sheet field names differ from the configured defaults by resolving configured watches through alias-aware lookups and probing only the still-unresolved aliases. Fixed repeated Roll20 parser errors from fallback death-save probes by removing character-id references ( @{<id>|attr} ) and using safe character-name probes instead. Fixed repeated startup and sync errors caused by asking Roll20 for death-save field names the current game sheet does not define. The resolver now keeps a persisted game-wide field-name status cache ( state.HealthColors.dsFieldStatus ) so proven-good names are reused, rejected names are not retried, and the cache is cleared automatically when the GM reconfigures death-save fields or manually resyncs after a sheet change.
The Aura/Tint HealthColors API version 2 has been updated and is available in the OneClick Installer. [2.3.0] – 2026-10-06 Added Selectable heal/hurt effects   —   !aura heal <effect>   and   !aura hurt <effect>   now accept a Roll20 built-in effect name (e.g.   glow-holy ,   explode-blood ,   splatter-blood ) or a custom FX name/id from the campaign's Effects menu, as well as the existing 6-digit hex colour.   !aura heal default   /   !aura hurt default   restore the shipped colours. ( #5 ) Added   !aura listfx   (and a   List FX   button in the GM menu) that lists the campaign's custom FX with their ids and one-click   Heal   /   Hurt   set buttons, plus a reference of the built-in   <type>-<colour>   effect names — restoring the   LISTFX   helper from the 1.7.1 forum build. Added a per-character   USEHEAL   attribute mirroring   USEBLOOD :   DEFAULT   (use the global setting),   OFF / NO   (no heal FX for that character), a hex colour, or a comma-separated list of built-in and/or custom effect names. The GM menu and   !aura settings   snapshot now show the chosen heal/hurt effect (colour swatch for hex values, the effect name otherwise). One-Click install options   — every setting (bar, aura/tint, palette, thresholds, PC/NPC toggles, nameplates, aura display values, FX, death sound, Death Save Integration) can now be set from the Roll20 One-Click install dialog via   useroptions . Options are applied on first install and whenever the dialog is saved again (tracked in   state.HealthColors.globalconfigCache.lastsaved ), so in-game   !aura   changes are not overwritten on every restart.   !aura reset   /   !aura reset-all   return to the One-Click values. script.json   now declares the objects and properties the script reads and writes at property level ( graphic.* ,   character.* ,   attribute.* ,   custfx.* ,   jukeboxtrack.* ,   Campaign.token_markers ). Changed USEBLOOD   now accepts Roll20 built-in effect names alongside custom FX names and hex colours.   OFF / NO   keep their long-standing meaning of disabling all HealthColors FX for that character and are now matched case-insensitively. Unknown effect names given to   !aura heal   /   !aura hurt   are rejected with a GM warning instead of being silently ignored, and the previous setting is kept. A configured custom FX that no longer exists (global setting or character attribute) now whispers the GM once per setting change rather than on every HP change; the API log still records every fallback. The warning names the setting or attribute to fix. Built-in effects are spawned by name with Roll20's own renderer, so they play at Roll20's fixed size and are not scaled by token size or damage amount. Custom FX and colour bursts keep the existing scaling. Updated the Death Save Integration sandbox guidance for Roll20's September 2026 rename: "Experimental" is now   Mod Script Sandbox v1.5   and "Default" is   v1.0 . The script now reads the running version from   Campaign().sandboxVersion , logs it at startup, reports it in   !aura deathsaves debug , and only shows the Beacon sheet note in the GM menu and the one-time GM whisper when the game is on v1.0 (or the version cannot be determined). Fixed Fixed newly placed tokens staying uncoloured until a setting was toggled (reported on the Roll20 forum with the 5e Shaped sheet, where HP max is calculated by the sheet after the token exists). A token change that only altered the health bar's max, its attribute link, or the token's character was treated as "nothing relevant changed" and skipped, and the   change:attribute   listener ignored changes to an attribute's max. Both paths now re-evaluate the token (silently, with no FX) so the aura or tint appears as soon as the bar becomes usable.