Yes, you can do this. You'll need ShowButtons , the MetaScriptToolbox, and a script to handle copying/creating the ability text. I know InsertArg can create an ability... and it can copy an ability from one character to another. There might be a cleaner script solution for this part, but I know IA so I'll use it. You'd have 2 commands for each "condition" you were trying to set up this way: The first command would set up an ability on the character sheet; the second command would be the one set up. If you have any trouble creating the second ability (because it will be multi-line), you might need a third ability to serve as the "source." Then you would want to use ZeroFrame batching to make sure there were no dropped lines, since each would be multi-line commands. The set up command would look something like: !{{ !ia ...arguments... !showbuttons --show Character Name|ConditionAbilityName }} I will have to refresh myself on InsertArg syntax for copying between characters (and/or the syntax for constructing a command line). In any case, once you correct the IA line, you'd run the above and you'd get a button created on the character, followed by ShowButtons making that button be visible in the Token Action Bar (it might be necessary to deselect and select the token if you don't see it). The trick is to create the secondary ability as a multiline command, too. If you have trouble creating a multiline command, you can have the ability pre-created on a macro mule character and copy it from there. The command line you create in-game will be straightforward: !{{ (^)&^{template:default}{{name=Condition Name}}{{Effects=Something}} !ia ...arguments... }} In other words, the ability that displays the condition info (the one that is assigned the token action button) either deletes *itself* using InsertArg (if it can -- I forget now). If we can't lay our hands on a script that *will* delete an ability, we can write one quickly enough. However, we could also use InsertArg to rewrite the text of the ability to be an empty string, then use ShowButtons to make sure we no longer see that ability as a Token Action Button. As I said, I'll have to look into the syntax for InsertArg to refresh myself. I'll do that tomorrow and if I can figure out the write sort of line, I'll post back.
