Hi all, I couldn't find where this was being mentioned anywhere else. I have been using a script for a while to manage the count on a token's status counters when the token's turn starts. This is done with the event "change:campaign:turnorder". Recently, I can't say when exactly when, I noticed that it was deducting the count on two tokens each turn at the start and end of a turn. Basically, I found that the event is triggering twice when the turn order advances. After figuring this out, I built a state.turnorder and an if/else statement to detect when the first event called (the token finishing it's turn is moved to the bottom of the list) and when the second event is called (when the next token is moved to the top of the list) to figure out when to trigger my API. But here's the kicker: in my copied instance where I develop this is happening 100% of the time. In my live game the douple trigger is NOT happening every time and so my if/else causes a random staggering to the status count deduction. Has anyone else encountered this? I've been all over the API documentation and cannot find this mentioned anywhere. I have another API making use of the event "change:campaign:turnorder" but it isn't having the problem since I keep track of the state.lastturn for that API to announce when it's a new token's turn so that way I ignore the first event. It looks like I might need to be doing this for every turnorder API.