Many of the pages on the wiki were made my the community, not the devs, so a comment like "doesn't appear to be usable" comes about because users have tried to make them work and havent succeeded. It doesnt imply that staff have any intention of changing a function in the future, it's just an observation by users to other users. As you've found, most uses of javascript are blocked - we can manipulate attributes, and thats basically it. Through that we have some ability to influence CSS, because they can read hidden input values. Pete L. said: Whilst playing with sheet worker scripts etc the only thing thats really annoying is that I can't call the roll command from them, so I can't make rolls affect attributes on the page. I think you could do almost anything if they would allow this, allowing you to track extended tests etc. Depending on what exactly you need, you might be able to do something. Action buttons let you trigger sheet workers, so you can simulate rolls with Math.random, but you can't print out the roll to the chat. You can track consumables, etc. If you trust your players, you could have an action button simulate a roll a(and update any needed attributes), and save the roll output to an attribute. Then use a roll button that prints that attribute to chat - so you get the simulation of a roll. It would be two buttons to click, and you'd have to trust the player not to keep rerolling the first one till they get what they want (though there are ways to check that). It's not ideal, it is a bit clunky for general use. If you have access to Custom Sheets, you have access to API scripts and they provide a better solution to this kind of thing.
