Andrew is correct about some script solutions, but you might be able to do it even short of that. Certain properties are available via Roll20 syntax... like bar values: @{selected|bar1} @{target|bar1} You CANNOT get a bar value from Roll20 syntax when using a name, however: @{Ruby|bar1} NOTE: This DOESN'T work ...because you could have any number of tokens on the board representing the character "Ruby." Back to the Roll20 formations that work... while you can use both the @{selected} and @{target} syntax in the same command line (and they will both resolve to values), when you use an @{target} construction in the command line you lose all of your selected tokens for the purpose of the message. Your @{selected} constructions will resolve but there will be no selected tokens when the message reaches TokenMod... which normally wants to operate on the SELECTED token. But you can work around this a bit. Option 1 TokenMod also allows you to designate the IDs of tokens to work on (instead of looking for selected tokens, it will work on the ids provided). If a non-GM wants to do this, you have to configure a setting in TokenMod, but otherwise GMs can do this natively. So one option is you can use the --ids argument for the receiving token, and use @{target} syntax to get the values you want. Let's say you wanted to copy the bar1 current and max values from one token to the other: !token-mod --ids @{selected|token_id} --set bar1|@{target|Pick Source|bar1}|@{target|Pick Source|bar1|max} Or, if you didn't want to have to select the destination token every time (to use the @{selected} syntax), you could use the hard-coded token id instead: !token-mod --ids -ORzDcN_9lq8G40BtRF_ --set bar1|@{target|Pick Source|bar1}|@{target|Pick Source|bar1|max} Option 2 The MetascriptToolbox will work in the TokenMod command and do things for you, including letting you designate a token to "virtually select". The token isn't *actually* selected on your board, but the message (and TokenMod) will act as if it is. Then, instead of using the --ids argument for TokenMod, you could use an {&select} formation instead: {&select @{selected|token_id} } ...or, again using the hard-coded id: {&select -ORzDcN_9lq8G40BtRF_ } That command line would look like: !token-mod --set bar1|@{target|Pick Source|bar1}|@{target|Pick Source|bar1|max} {&select -ORzDcN_9lq8G40BtRF_ } ...and doesn't require any TokenMod configuration to allow players to use IDs. Option 3 Use the Metascript Toolbox, but use Fetch to read the values for you while you keep the destination token selected: !token-mod --set bar1|@( -ORzDiK1FBXQ6_5IUSPz. bar1)|@( -ORzDiK1FBXQ6_5IUSPz. bar1_max) Although, if those tokens have names and they are *uniquely* named on the current page of your game, then you could use their names, instead, to make it more readable: !token-mod --set bar1|@(Julius Squeezer . bar1)|@( Julius Squeezer. bar1_max) Bonus If you don't want to have to select the recipient, you can combine the above Fetch constructions to get the token_id of the recipient by name, and use it in a {&select} tag from the previous option to arrive at a command that is pretty hands of. Go Forth There are more ways to set this up using the Toolbox, and that doesn't even get to the capacity to do this with ScriptCards that Andrew mentioned... so there are a lot of options to do what you're looking to do! If one of these doesn't work, post back with more specifics and we can get you sorted.
