TurnMarker1 Stopped Working on New Pages

I have been using TurnMarker1 for multiple years now and love it. Recently I noticed that it sometimes wouldn't work when I started a combat. I worked through the boundaries of the issue and discovered that it still works on pages where I had used it previously, but if I create a new page the marker is never placed on the tokens. I thought at first this may be a Jumpgate issue, but I have verified it in non-Jumpgate games as well. If I create a brand new game and add the script to it, the default first page works correctly, but none of the new pages work.

Hi, Carl... that script hasn't been updated in 2 years, so I doubt whether something has been changed in the code. That said, Roll20 rolled out mod updates in... April... I think it was. I'll see if I can poke the Arcane One and get him to take a look at what might be going on.

Hmm. That's mildly distressing. I'll dig into reproducing this.

Aaron, don't worry about it. The problem was between keyboard and chair. I didn't have the party ribbon on the pages I was testing on. I feel like an idiot

Ah!!  I literally just pointed that out on a script to one of the devs yesterday, so you're in good company. I should have thought of that!

FWIW - I've noticed the same thing about TurnMarker1 and it's definitely frustrating that the player ribbon must be on that page. What if I have combat with just 1+ players on a separate page while the rest of the party is somewhere else and not in combat? Or if combat is spanning multiple pages? It also, like everything, leads to wasted 15-20 minute debugging sessions only to realize "the marker will only show on the player ribbon page even though every other part of the script works outside of that page". There's also some wonkiness with actually adding tokens to the initiative making the "rounds of combat" go up, even though combat hasn't officially started. It'd be nicer if this script only activated via a script call and wasn't attempting to be "automatic". You already have to make a separate script call just to reset the turns back to 1. I've decided to just do a small re-write so that it works more effectively and regardless of the page. And also doesn't "move" the token, since moving the token means it could reveal where certain creatures/things are without the players having actually known that information (aka metagaming).