You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No Create/Edit button on the failure special node (in scenedit)
How do I target the position that's targeted, for example, in an Explosion on Space node? Are there special negative-number coordinates that reference the targeted position? Can we make this easy to figure out?
Neither the node, nor the failure node, is called
If you trigger the node with a PC's last AP, the next PC in the rotation becomes the caster
The text was updated successfully, but these errors were encountered:
No Create/Edit button on the failure special node (in scenedit)
Once #607 is dealt with, this should be taken care of.
How do I target the position that's targeted, for example, in an Explosion on Space node? Are there special negative-number coordinates that reference the targeted position? Can we make this easy to figure out?
Yes, there are special magic numbers to reference the chosen location. I believe they're the ones documented here – so, either -21 and -22 or -10 and -11. I don't remember which.
Neither the node, nor the failure node, is called
I'm pretty sure it worked when I implemented it… although…
If you trigger the node with a PC's last AP, the next PC in the rotation becomes the caster
I don't remember if I ever tested the node in combat.
I don't remember if I ever tested the node in combat.
It might also be the case that if you put the node on an item, APs don't get taken until targeting ends. I was testing with the node just placed on a tile for the party to step on, which may be an unusual usage (but should work, imo).
Yes, there are special magic numbers to reference the chosen location. I believe they're the ones documented here – so, either -21 and -22 or -10 and -11. I don't remember which.
Oh, your location picker (#562) should have a button for putting in those magic numbers.
The text was updated successfully, but these errors were encountered: