Makin said: I love this API! It's incredibly helpful in so many ways. I'm really hoping to be able to combine all the work of showing, tracking, and calculating status conditions through the token markers, but I have no idea how to do it. It seems like it's possible based on other comments in the thread, but I'm clueless where to even start. I've set up custom status markers to represent conditions, and can apply them to tokens for whatever duration I need. My goal is to be able to add a condition/buff either directly to a token from the radial menu or through the CombatMaster API chat menu, and to simultaneously apply the associated condition(s) or buff(s) to the character sheet that the token represents. Then have the condition/buff removed from the sheet when the buff/condition falls off the token from the duration expiring or by being manually removed using the radial menu again. Is there a way to set this up using CombatMaster? If there is, does anyone have an example of how to set a condition/buff up this way, and I could fiddle away from there? For reference, I'm using the Pathfinder Community Sheet, which has "conditions" built in, and "buffs" which have to created on the sheet. Even if this isn't possible, the API is still amazing! You'd need the script ChatSetAttr for this, and you can set up each condition to run an API command for that script when it's added or removed. You'd need also need to know the name of the condition attribute on the sheet, or the repeating ID or row number of the custom buff. Next you'll need to set up a substitution for character ID in CombatMaster, in the Macro & API setup. It needs to be a string that won't be used anywhere else; for example, I use charidentifier . Then go to a specific condition in CombatMaster. For the API parameter under Adding, you'll enter a command like this to activate the condition in the sheet, replacing the bold parts with whatever applies to your settings/sheet: {{!setattr {{--charid IDsubstitution }} {{-- condition_toggle_attrbute |1}}}} Normally, the command wouldn't have the brackets, but they're necessary when adding the command to CombatMaster. For the API parameter under Removing in that same condition, you'll enter the same command, but replace the 1 with a 0.