Unfortunately, the homebrew-ability of Demiplane (and Beacon) sheets is... lacking. You've already discovered that you can't just edit the sheet -- but that's the same for any Roll20 sheet (you can download and edit community sheets but not Roll20 sheets). Another approach that you might want to try (and would be disappointed to find that it doesn't work) would be to create a custom attribute on the sheet. That, at least, would give you current and max values and the ability to reference those in chat: @{Character Name|Wrath} ... or ... @{Character Name|Wrath|max} Again... this really won't work. First of all, you can't easily change them (you'd have to go to the "Advanced Tools" tab on the character sheet), and you can't change them with a script (because Demiplane attributes aren't properly exposed to the API). Second, you can't link that attribute to a token bar value... one of the weaknesses of Demiplane and Beacon sheets is that only those things that have been exposed by the devs can be linked in a token bar. In other words, if the devs haven't anticipated your need (and built the supporting infostructure AND exposed it), you can't do it. So what CAN you do? You CAN add a non-demiplane character for each player to control, and it doesn't require a "second" character sheet. If you hit the "+Character", it will ask you for the name, and then it will create that character in the "default" sheet environment. Since these sheets are really just a connection to the Firebase storage on the backend without the interface of the Demiplane build, they behave like legacy sheets (non-Beacon and non-Demiplane). That means you can create an attribute on each player's secondary sheet and link the attribute to a bar, then add those tokens to the board and let the player control them. That would introduce another token for the players to control (not ideal), but it would give immediate "at a glance" awareness of the resource, and it would let you use ChatSetAttr (or probably TokenMod, if you had the bar linked) to modify the value. Orrrrrr.... another option would be a chat menu "panel" that depicted the resource as a pseudo-bar interface, providing buttons for modifying the resource from there. Players could whisper the panel to themselves, then use buttons to modify. None of these are *great* solutions, but this is the boat we're in until Roll20 stops locking the sheets into a "whitelisted-behavior" approach.