You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A script check runs only where no other player can edit it. Before, a player's script ran in the GM's browser with the GM's rights whenever the GM evaluated that blueprint: at the start of the player's turn, or through an aura on an NPC's roll. Now the GM runs scripts only on documents no player owns, and a player runs only their own. Elsewhere the check fails, and the Test tab says why.
The GM checks who asked for a change. A change a player's reaction sends to the GM must touch something that player owns, or a creature on the scene they are looking at. The sender now comes from Foundry, not from the message. Each field of the change is checked before it is used. Rest triggers run only for the player's own actors. Demanded-save answers are accepted only from the player who was asked.
Fixed
Counter changes add up. Two results changing the same counter on one roll (for example, two "+1 combo" blueprints) used to count once. With a GM connected, counter changes are made one at a time from the stored value.
A cancelled roll spends nothing. Closing the roll dialog no longer uses up a limited bonus ("once per turn") or a rider. The build-n-action.applyResult hook now fires for a roll's results once the roll actually goes ahead.
Riders no longer overwrite each other. A rider added by one client while another client uses a different one is kept. Riders are now stored by id; a list stored by an earlier version is converted the first time it changes.
Development
npm run release works right after a version bump: every build writes the root module.json, and npm run check builds before it tests.