Varsuuk
May 27th, 2021, 06:23
Anyhow, Wizard of Oz references aside...
I created a spell action which is really better called a spell damage action. I created a saving throw roller. Now, it hit me that I really never looked at how this works and the right way to automate. My original thought was to just create the saving throw - have the person click and if failed they click the spell for the damage (or effect).
I figured I'd add a mod button for like 1/2 etc to press if that applied.
Then, thought why not include more functionality in first try. Well, probably because my head got mixed up looking at 5E for ideas on how casting works (was going to look at 2E tomorrow in case it is clear since I am more familiar with 1E/2E terms but suspect even if how it worked changed the names/types are probably reused from 5E)
Like, in broad strokes, how does it work?
Press a "cast" action that triggers a saving throw on target(s).
Resolve the roll(s)
First question is how the results of the roll are persisted for the next step to reference.
Next, the caster presses an effect/dmg button and that roll executes, checks someplace for results of the save (if allowed) and apples the damage.
(if anyone can suggest a good place to put printstack in 5E/2E to better follow things, let me know)
Perhaps there is a tutorial write up here or on YouTube for this sort of basic pattern?
Appreciate your time, night all
--Dan
EDIT: I need to get sleep, it's 1:30am but I skimmed manager_power and saw one method calls performMultiAction with an array of rolls. So maybe the acts are all "joined" in some way after all? Didn't try to read it, just after a game and late night helping son write a paper... brain fried ;)
I created a spell action which is really better called a spell damage action. I created a saving throw roller. Now, it hit me that I really never looked at how this works and the right way to automate. My original thought was to just create the saving throw - have the person click and if failed they click the spell for the damage (or effect).
I figured I'd add a mod button for like 1/2 etc to press if that applied.
Then, thought why not include more functionality in first try. Well, probably because my head got mixed up looking at 5E for ideas on how casting works (was going to look at 2E tomorrow in case it is clear since I am more familiar with 1E/2E terms but suspect even if how it worked changed the names/types are probably reused from 5E)
Like, in broad strokes, how does it work?
Press a "cast" action that triggers a saving throw on target(s).
Resolve the roll(s)
First question is how the results of the roll are persisted for the next step to reference.
Next, the caster presses an effect/dmg button and that roll executes, checks someplace for results of the save (if allowed) and apples the damage.
(if anyone can suggest a good place to put printstack in 5E/2E to better follow things, let me know)
Perhaps there is a tutorial write up here or on YouTube for this sort of basic pattern?
Appreciate your time, night all
--Dan
EDIT: I need to get sleep, it's 1:30am but I skimmed manager_power and saw one method calls performMultiAction with an array of rolls. So maybe the acts are all "joined" in some way after all? Didn't try to read it, just after a game and late night helping son write a paper... brain fried ;)