Constitutional Amendments can handle things like this: https://forge.fantasygrounds.com/shop/items/42/view
Printable View
Constitutional Amendments can handle things like this: https://forge.fantasygrounds.com/shop/items/42/view
Okay. I am aware of Constitutional Amendments, but it fails to load correctly for me and breaks my HP tracker translating from sheet to combat tracker. I have posted up the errors in their forums, but I was hoping I can bypass it with BCEG. I appreciate the response.
*Edit -- Constitutional Amendments on the forge is currently broken, but a fixed version is on the github, so I will get er' loaded up and give it another shot!*
Version update v5.40
Fixed: DMGA firing multiple times when used with SAVEA
Fixed: MASTERY conditional when using Advanced Effects
Fixed: Script error when using all descriptor in some cases
Fixed: FG locks when SAVEA applied to multiple targets simultaneously
Can anyone provide an example of how CSTRIKE can be used to automate Cunning Strike, and how it works with RAKISH? I'm not sure of the syntax needed nor how it allows you to decide on what effect to use. Thanks in advance!
Set up a power effect on the action tab
CSTRIKE: poison
set it to [roll] and also set it to [self] with duration 1
Apply the effect either before the attack or before the damage roll. It will subtract the appropriate sneak damage dice and apply the CSTRIKE automation, if there is any.
You can also do something like the following if you want to do both
CSTRIKE: poison,trip
If you don't have enough sneak dice to do said CSTRIKE, it will ignore it.
Got this a bunch of times today.
It occurs when only BCEG and Requested Rolls are loaded and a Save is rolled. I'll cross-post.Quote:
[ERROR] Handler error: [string "..erCombatEffectsGold:..on_save_dnd_bce.lua"]:879: attempt to index field 'sSaveDesc' (a nil value)
Specifically, it only occurs when a DC is set for the roll. This issue also occurs for party sheet rolls with DCs. ActionSave.onSave() checks for rRoll.nTarget before calling notifyApplySave, which is why rolls from the character sheet don't trigger the error. This does not appear to be an extension conflict.
Ah, nice - I can confirm that you are correct and that the same error comes with only BCEG loaded on a party sheet with DCs. Thanks for the speedy response!