No more crashes when removing conditions from the turn announce box, ad-hoc or otherwise =D I am still getting these bugs, however: Persephone said: Assigning a marker via radial menu is now applying the condition's
defaults, but is adding the marker twice (so two of the same marker on
one token). Everything here is working as expected, besides the extra marker. GIF: Clicking name of an ad-hoc condition in turn announce crashes API Console log still shows command as !cm instead of !cmaster (might confuse new users) I'm unsure if these ones ought to be considered bugs or just limitations, so idk if you want to bother with them: Persephone said: Assigning a marker via TokenMod currently is not applying the condition at all, just the marker. Example command (entered directly into chat; 'enrage' marker is linked to the Rage-Cooldown condition). TokenMod is doing everything it should, but CombatMaster is not registering the marker being assigned. !token-mod --set statusmarkers|enrage GIF: Here's what happens when I set up Raging to run this command when it's removed. Same as above, the enrage marker is applied, but the Rage-Cooldown condition is not. It's the same marker used to apply that condition in the first GIF, so I know they're linked properly. !token-mod --api-as playidentifier --ids tokidentifier --set statusmarkers|enrage GIF: