Hi Moon Wizard,
I think this recent update may have broken the SAVEADD effect. Here is a breakdown of what i found in the code:
The Issue
In the updated manager_action_save_dnd_bce.lua, the save resolution callbacks are still invoking the function as:
This passes the arguments as (target, source).Code:BCEManager.addEffectFromCompData(rActor, rOrigin, tCompData)
The Cause
- addEffectFromCompData passes those arguments directly to notifyAddEffect.
- However, notifyAddEffect now expects (source, target).
- Because of this, the arguments are currently swapped for save resolutions in the update.
The Impact
This breaks SAVEADD effects on saves. Instead of applying the effect to the save-rolling creature who failed, it applies it to the caster.

