Several serious initiative tracker bugs

In our last game yesterday we encountered a full row of severe bugs: Initiative entries got duplicated with different values, probably where token actions where not correctly applied Changes were only applied partially, probably where token actions where not applied correctly The used macros were mainly: /w gm @{selected|token_name} has INI [[(?{Initiative|0}+?{Initiative Dice|1}d6) &{tracker}]] /w gm @{selected|token_name} ends round [[10 &{tracker:-}]] As well as manual adjusting the value in the tracker and i think this breaks the whole linking and can cause problems. Some tokens are associated with characters some not. Some generics i simply copy/pasted but I expect this works. Tokens were on object and GM layer. OS Type,OS Version,Browser Type,IP Address,Javascript Enabled,Cookies Enabled,Color Depth,Screen Resolution,Browser Window Size,Flash Version,User Agent Windows,Windows 7,Chrome,80.110.112.137,Yes,Yes,24,1920 x 1080,1920 x 995,17.0.-1,"Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.90 Safari/537.36"

Do you have any API scripts that are running?

No I haven't. But all players edit their initiative and use the token actions on their on. Also I as GM do edit their initiatives and use token actions. All tokens are under control "all players" and most of them have been copy/pasted - I do not always rely on drag and drop out of the character list as this is sometimes annoying (I do not prepare one time grunts)

Are you removing the existing turn order entries when you move to a new page? Turn order entries are tied to a specific token in a specific page. If you have Ragnar on the Bridge page and the copy paste him on the Castle page, when he rolls his initiative you will have two Ragnars in the list. If you point to one of the Ragnars, you can see a highlight around the one it refers to. I suspect this is what is happening for you.

I do in fact have the same tokens duplicated on multiple pages but the combat happened one a single what happened was the following (with the token command above): New page New combat Clear Initiative tracker Player1 rolled initiative 14. Initiative Tracker showed "Player1 with 14" Player2 rolled initiative 12. Initiative Tracker showed "Player2 with 12" ... NSCX rolled initiative 10. Initiative Tracker showed "NSCX with 10" - so far so good - .... combat round.... I change some of the values manually, so do some of the players (mistakes, special actions, etc) I announce "end of round" All players click on their token (on the same page) and I repeat this step for NSC1 to NSCX: Select Token End of Round Token Action Player1 ends round. Initiative Tracker showed "Player1 with 4" Player2 ends round. Initiative Tracker showed "Player2 with 2" Then we repeat 9 to 12 until all combat rounds are over. After that we beginn by 4 again for the next combat round until the combat is over (shadowrun initiative system). Somewhere after 10. with some of the token actions I had duplicate values for Player1, NSC1 not linked to any tokens anymore. They were manually changeable but were not affected by token actions. I also do use copy paste of Token NSC before step 3 for NSC1 to NSCX but they are not linked to any character and also not all of them duplicate the initiative (at least 5 NSC but only 1 or 2 characters had the problem) I would love to give you a more helpful feedback, but we stopped using it as we did not want to start debugging during a roleplaying session.

That's very bizarre. It sounds tedious, but are you able to duplicate the behavior with just you in the campaign?

Didn't manage it. Let's ignore this thread until it happens again. We will play on sunday and on may,11. If it happens I will try to reproduce the steps exactly.

Today we played again, the used makro was: /me würfelt Initiative [[?{Initiative Attribut|0}+?{Initiative Würfel|1}d6sacs>70cf<0&{tracker}]] für @{selected|token_name} And sometimes it simply did not update the tracker for one character, but for the others it did. It was like the token got out of sync and even calling the macro again and again did not change the initiative anymore and it did not issue any chat messages :(. I am sadly still unable to reproduce it.

I'm wondering if it's possible an encoding issue with the umlaut character. Perhaps you can check if it's only happening to characters with those types of characters?

This is very unlikely the text message with "würfelt" is always the same and it happened to the character named "Foxy"

Alright, next time it happens can you capture the console log to see if the client is throwing any errors when it's failing to update the tracker?

Damn it.... why haven't i thought of that. Thank you, yes i will definetly do that and post it! From the initial posts one thing has changed, now i am runing api scripts (as the post of Aaron made me aware that they exist) but the problem existed before as well.

Alright. We'll look at all the pieces once you're able to see the errors or if you figure out how to replicate the issue.