So I'm working on a new sheet for a new system. This system uses a pooled die mechanic, where each die represents one aspect of the action; typically skill + attribute + equipment. So lets say you are attacking someone, you would roll Combat (1d10) + Agility (1d8) + Sword (1d6), add them all up and try to beat your opponent. 1's on any die should be considered a "fumble", and have implications; If the d6 came up a 1, you just dented your sword and now it's a d4. Thats the gist of it. So I'm using inline rolls, because I have to have the total. If I break up the toll into attributes for a template roll, then I can't sum them. This was very surprising to me, but it seems that the intent behind the template is to represent different rolls which do not interact with each other, and thus cannot be summed. Now, this actually works with inline rolls like: /roll 1d6[sword]+1d10[combat]+1d8[agility] But god that looks terrible. And I don't seem to be able to access the labels at all within the roll template, nor any of the aspects of the inline roll which I can much more richly interact with via the API. I see that I can use allProps() to iterate over the key/value pairs in the template input, but since I need the sum I was forced to send that as a single inline roll. Are there any other interesting undocumented ways to interact with a template input than via the key/values exposed by allProps()? Can I get at those labels somehow? Is there a hidden way to sum up multiple properties sent to a template roll? I'm not married to the inline roll, and could easily refactor this to just send each attribute to a template if I could actually sum them all within the template. If neither of these are options, where do I begin looking into how to intercept the roll with the API, and render roll-template-like output as a hack/workaround. I'd really rather avoid this because it would make the charsheet dependent on an API script. TIA!