Hello! I like the "emote as" functionality provided by the GM /emas command. I've added the <a href="https://wiki.roll20.net/Script:emas" rel="nofollow">https://wiki.roll20.net/Script:emas</a> script to give this functionality to players in my game along with general macros to roll for initiative/hit/damage, with the idea that the character name will always appear with that dice roll in the chat. This simple example initiative macro is 'broken': !emas @{selected|character_name} rolls initiative with @{selected|weapon_name} [[d10+@{selected|weapon_speed}[Speed]&{tracker}]] The output to chat seems correct, something like: > Gnoll rolls initiative with Teeth & Claws [6] But the initiative tracker will show the Gnoll as having rolled in with a different value, because somehow it's separately rolling the base d10, even if it's correctly adding the Gnoll's weapon speed. So the correct initiative band of values will be expressed in the roll to the initiative tracker, but it's almost always a different initiative value than the number displayed in the chat. Which of course, makes the flavor of always rolling with the character name now clash with the functionality of the game chat displaying conflicting values than the initiative tracker, even if the names of the tokens and the weapons they're rolling in with are correct. This is not an issue with the core /emas functionality available to GMs, but even if a GM uses the !emas script it will display this buggy behavior. My game has "token action" macros which are shared between everyone in the game, and these are the macros for initiative/to-hit/damage which I'd like to display character names at all times for all players and GM using the same token actions. Is there any way to work around this? I am hoping there's something clever which can be done with having the tracker read directly from the chat value even after the [[]] inline roll is complete with or without the tracker, or something to that effect. I'd like the tracker to reflect what's displayed in the chat, but I'm not adept with roll20 to know if there's a hacky way to get this working. I'm assuming the original script might be able to be updated, but I'm also assuming that's unlikely to occur or there are other barriers to prevent that from being useful (something like "all macro users then must have api access and be paid members" or something would be a barrier there). Any help is appreciated! Thanks for your time