I have also tried a multi-sided token, but I think the downsides is as you say in some of the possible solutions the multi step process in order to change the result of the tracker. I also tried the character sheet but gave up admitedly since I wasn't sure how exactly I could get the macro working and the main idea is to have a resource ability for it and also it wouldn't be visible to the players unless I hit or they hit the button to show much fear the GM would be holding. So in summary, I'm trying to see if a visible fear tracker (with the least amount of multisteps to update the score) is feasible without API. Gold said: The 2 methods you have, are pretty good. What's the downside of either, for you? I think the downsides might be... if you don't want to keep the Turn Tracker open all the time (because it takes up screen real estate).... Or with the Token you have to keep moving that token to whatever Map-Page the players are seeing. Another non-API method is: Create a Rollable Table Token (aka Multi-sided token). However this method has the same downsides as using an invisible-token with HP bar. You have to keep the multisided token in-view; and you have to use Choose Side to change the Fear to a different number. Another non-API method is: Create an Attribute (called Feartracker or something like that) on a Character (just put it on 1 character), and create a Macro to report that Attribute into chat. With this method you could add the Attribute onto just 1 of the PC's, and Query it via their Token. Name of the Macro button label: "Report the Fear Counter" Contents of the Macro code: The party has @{Selected|Feartracker} fear points! Then it's up to you whether to grant this Macro to everyone, or keep it for yourself the GM to trigger at will. But the downside of this method is similar, you have to change that Attribute stat to keep up with their current fear level. To make this slightly easier you could set the Feartracker attribute as 1 of the 4 bubbles/bars on the 1 PC. I think the advantage of this last method is, since you can store the attribute/data/number on a PC token, therefore you don't need to keep carrying around a separate token for this. Addendum: However I'm not sure of how the Attribute method would work if the game uses Demiplane character sheets. I do not know if a custom attribute can be added on that or not.