Release v5.13.0

Build Details:

FEATURES

Tokenizer 2 Integration: When the Tokenizer 2 module is active, a new button in the Identity heading of Token Appearance opens it from the Visage Editor. Save the token and/or portrait in the Tokenizer 2 window then close it. The saved images fill in the Visage's Token Image and/or Portrait filepaths. A token saved with a Dynamic Ring switches on the Visage's ring, uses the new image as its subject, and copies the subject scale and any ring and background colours you chose. A token saved without the ring switches the Visage's ring off. An oversized design also sets the Visage's Scale, so the frame still fits the grid. Each save is a new file named after the Visage with the date and time, so it never replaces art that other Visages or tokens use. The saved images are ordinary files, so the Visage keeps working if Tokenizer 2 is later disabled. Visage keeps only the images, not Tokenizer 2's layers, so opening Tokenizer 2 again starts from the flat image rather than the original design. While Tokenizer 2 is open, the Visage Editor can't be saved or closed. Only GMs see the button, because Tokenizer 2 holds a player's save until a Game Master approves it.

BUG FIXES

Restore spacing around tile grids in the Selector HUD and hide its background and border.

UNDER THE HOOD

Added src/integrations/visage-tokenizer.js. It uses only Tokenizer 2's public openEditorStandalone API (detected by checking the method exists, not by version number) and reads only the saved image paths and the ring and texture scale settings from its result. Tokenizer 2's layer stacks and flags aren't stored, so Visage data doesn't depend on its internal format.
New localisation keys under VISAGE.Tokenizer.

Navigation Menu