-
Your specific issue - passing data as part of the roll (steps 11 to 12), has nothing to do with OOB messaging at that part. It's the actual process of applying the damage (healing in this case) that uses OOB messaging as the GM needs to apply the damage/heal (step 14+).
As you've mentioned above, the issue you're having is making custom data available to the onHeal function, right? The asynchronous nature of the rolling process means that the resultHandler (onHeal) is kicked off sometime in the future, once the dice have landed and provided a result. The standard mechanism for passing info as part of a damage roll (which is what a heal roll is, essentially) is to do it in the description - usually with the info enclosed in square brackets. Try it - roll some heals/damage in the ruleset and see what FG puts together in the description.
https://dl.dropboxusercontent.com/u/...ive%20Text.jpg
In the 4E ruleset, manager_action_damage.lua the applyDamage function decodes the damage description with" local rDamageOutput = decodeDamageText(nTotal, sDamage);
-
OK, thanks, I'll give it a go :)
Edit: OK, got that working :)
Thanks for all of the help guys, both here and via PM - I really, really appreciate it!
Cheers