timmaugh said: You'll want to use Plugger. Plugger can dispatch an inline command (using constructions -- like inline rolls and query results -- from the outer command). If the dispatched-command is defined as a "plug-in" to Plugger, Plugger can return a value from that command to that location in the outer command, but for what you need, it doesn't sound like that's necessary. Assuming the "health bar" for your token is bar 1, and assuming the token gets an amount of life equal to the damage they do, you could have something like: !SomeAttackScript --dice|[[2d20]] {&eval}token-mod --set bar1|+$[[0]] --ids|@{selected|token_id}{&/eval} That would use the results of the first inline roll (the only one) in a sub-call to TokenMod (everything between the {&eval} and {&/eval} tags). If you need to perform math on that inline roll for the Plugger call (for instance, if the life steal is some equation based on the roll result -- like 50% of the value), then you have 2 options. Option 1 First, you can wrap your inline rolls into a single stack and extract them where needed: [[ floor([[2d20]]/2)]] Since the Plugger syntax is removed from your outer command line after it runs, and since this roll is what the embedded Token-Mod call would want, you can put the Plugger statement before the outer script needs the inner roll: !SomeAttackScript {&eval}token-mod --set bar1|+[[ floor([[2d20]]/2)]] --ids|@{selected|token_id}{&/eval} --dice|$[[0]] ...or I believe you can use "computed" with the original order (where the inner roll is needed before it is calculated): !SomeAttackScript --dice|$[[0.computed]] {&eval}token-mod --set bar1|+[[ floor([[2d20]]/2)]] --ids|@{selected|token_id}{&/eval} Option 2 You won't always be able to conduct all of the math you want to do with inline rolls just by stacking them. There are times when you need the values for more computations than the Roll20 parsers allow. For times like that (or if you just prefer to work differently), your other option would be to use ZeroFrame to extract roll values and/or defer secondary rolls: !SomeAttackScript --dice|[[2d20]] {&eval}token-mod --set bar1|+ [\][\]$[[0]].value/2\]\] --ids|@{selected|token_id}{&/eval} Extension by SelectManager The above examples use the --ids argument of TokenMod because it is being called by another API script. In those cases, the message doesn't contain a set of selected tokens, so you have to instruct TM what tokens to take action on. However, if you have SelectManager installed, you won't have to include that --ids argument for TokenMod, because by the time TokenMod sees the message, SelectManager will have supplied the selected token(s) to the message working its way through the set of installed scripts. Extension by Fetch Fetch is yet another metascript that can retrieve token- or character-info *after* Roll20 parsers have had at the message. This can be important if you need to handle token-specific actions, and need to pull differentiated info into your command line. Most times this would be a case where you were using the forselected handle of SelectManager to issue separate Token-Mod calls for each selected token (if a bunch of tokens might get a benefit from the life steal, for instance). I don't think this is immediately applicable to your situation, so I won't clutter this with an example other than just to mention that the possibility is there. Thank you both for the help this has been really informative! I definitely think this will work for me and I shall be tinkering with it to get the hang of it, if I do run into anything that I can't seem to figure out should I make a post on the API forum about it or could I potentially send you a message tim?
