Help for 2 related questions!

1. I wrote a macro that calls an API script. (I wrote 20, actually).  My players with GM permissions can use the macro, but get an error when given player-only permissions. Is this intended behavior or have I made a mistake? Is there a work-around or another way to approach this situation? 2. My macros are all of this nature. Is there a better way to modify attributes on a character sheet? /emas "@{selected|character_name}"  gains +1 Award Points! /emas "@{selected|character_name}" increases AwardPoints from [[@{selected|AwardPoints}]] to [[@{selected|AwardPoints} +1]]! !setattr --sel --mod --AwardPoints|1

The /emas might be the problem here. I dont think non-GMs can use that command.

There is a script to allow players access to the /emas functionality which may solve the issue:&nbsp; <a href="https://wiki.roll20.net/Script:emas" rel="nofollow">https://wiki.roll20.net/Script:emas</a>

Thank you! It was definitely the /emas command which was breaking the script when I tested it with other players!&nbsp;&nbsp; And thank you for pointing out the Emas script -- that may be a better formatted fix than the awkward formatting when I switch from /emas to /em.&nbsp;

Quick follow up question.&nbsp; Switching to !emas API script worked in almost all cases, but I'm getting unintended behavior in this one particular script. The number being sent to the Tracker is not the same as the number being posted in the text chat emote. I can fix this by simply not using !emas for this script but I'm trying to understand where this is going wrong.&nbsp; !emas "@{selected|character_name}" rolls a turn order of [[1d100 &amp;{tracker}]]