Skip to content

v5.5.1

Choose a tag to compare

@github-actions github-actions released this 30 Jun 11:25
3ac873e

Release v5.5.1

Build Details:


BUG FIXES

  • Light settings on default token snapshots: Fixed an issue where base token snapshots were unintentionally stripping out native Foundry light properties not explicitly used by Visage, which could cause a token's default lighting to stop working. Because we cannot safely automate a migration without risking the overwrite of intentional user lighting setups, two new tools have been added to the Visage game settings menu. GMs can now manually use "Sanitize Selected" or "Sanitize World" to repair broken tokens by resetting their light schemas to Foundry defaults. These settings should only be used if you are experiencing problems with token lighting after using the Visage module.
  • Fixed an issue in the PF2e system where Visage would incorrectly revert a token's autoscale property to true when returning to the base token scale. Visage now correctly restores the property to its original state, respecting tokens where autoscale was manually set to false.
  • Fixed an issue where Visage would incorrectly capture automated token changes (such as the Rideable module altering a token's scale) as manual edits, causing the underlying token to become stuck at the wrong size or scale.
  • Resolved a visual bug where active Sequencer effects would fail to realign themselves if a token's physical dimensions changed while a Visage was active.

UNDER THE HOOD

  • Increased the Visage Automation debounce timer from 50ms to 250ms to prevent network race conditions with third-party modules when using Foundry on cloud-hosted services.
  • Moved and refactored Visage payload generators from the data schema to the data controller to prevent legacy scale data from polluting database updates.
  • Implemented strict property ownership logic to protect the base token state from being accidentally overwritten by external module updates. To maintain Visage's non-destructive behaviour, its saved default state can only be changed manually by the user through the core Foundry token configuration window.