This is a small thing, but I am having trouble sending the result of a roll to an API using a button.  To get it to work I am trying to use the Reusing Rolls trick .  But I'm having trouble with the syntax (and/or it's not possible). As background I am setting up a game where your weapon damage type (slashing, piercing) can be affected by your opponents armor type. In my macro for the attack, I have a button that calls an api script that will do that calculations to apply the damage.  I first have it query the player/DM validate the damage amount before sending it to be processed.  So it looks like this: What I'd like to do is prepopulate the query with the Damage value.   My full macro is as follows: &{template:default} {{name=@{selected|character_name} attacks @{target|character_name} with @{selected|meleeweaponname1}!}} {{Attack=[[1d20+@{selected|meleetohit1}]]}} {{Target AC=@{target|ac} }} {{Damage Type=@{selected|meleedmgtype1}}} {{Armor Type=@{target|armormaterial1}}} {{[Damage](!ApplyDamage2~@{selected|token_id}~@{target|token_id}~?{Damage|$[[1.computed]]}~@{selected|meleedmgtype1}~@{target|armormaterial1})=[[@{selected|meleedmg1} + @{selected|meleedmgtotal1}]]}} mytriggerkey #FX The relevant bit is:  {Damage|$[[1.computed]]} It almost works.  What I get prepopulated in the query is:  Rolling 1d8 + (2 * 1) + 2 = (4)+(2*1)+2'>8 And what I'd like, of course, is just the final result of that calculation.  I don't know if it's possible to get just the final result some way, or use javascript in the macro to trim to just everything right of the > symbol?  Or would I just have to send that result to my script to handle without letting the player validate? This is just a nice-to-have, anticipating players making the obvious request.  But if anyone can point me in the right direction or tell me not to waste further efforts in this direction, I'd appreciate it! Edit : I've decided that I can just allow players to hit enter with the above string in place and handle it in the script if we're accepting the default damage value.  Otherwise they can erase it and input a new number.  That works well enough for me, but if there's a right way to do it I wouldn't mind learning.