
Today we deployed some updates to the API Server! Is Drawing Split (Jumpgate) Jumpgate got a new setting for tokens that lets you individually specify if a token should snap to the grid and if it should have the UI (bubbles and menu buttons on select). In the UI, you can find those by right clicking the token and selecting Advanced Transform. On the API server, we've added two new properties on Graphic objects: disableSnapping -- set to true and a graphic won't snap to the grid. disableTokenMenu -- set to true and the bubbles and menu buttons won't be show on selection. These only have the above effects on Jumpgate of course. On Legacy, they are just aliases for the existing isdrawing property. Similarly, if you set the isdrawing property on Jumpgate, it will set both of these properties. This allows scripts to still function whether on Jumpgate or Legacy. For an example, you can look at TokenMod, which has been updated to add these properties. Handout .set() Crash There has long been a crash that happens when setting one of the text areas on Handouts (notes, gmnotes) and Characters (bio, gmnotes) while in a get call. What that looked like was: handout.get('notes', n => {
handout.set('notes', `${n}\nA new line!`);
}); This bug has been corrected now and the above construct will work as expected! Nested Rolls Bugfix There has long been a bug with nested inline rolls substituting the value of the result incorrectly. (I actually reported this in September 2019! ) What that would look like is is if you gave a roll like: [[1d6]] [[[1d8]]t[test-table]]] [[1t[test-table]]] The API would get back: $[[0]] $[[3]] 0 but expected $[[0]] $[[3]] $[[2]] This has now been fixed! This should clear up several issues that have been happening over the years with RecursiveTable and ScriptCards.