Printable View
SAVEA and DMGA are the only two things I know of that should execute immediately on a drop within range of something - however this seems to roll all the SAVES type of things also. I sent you a DM in discord with details.Quote:
Originally Posted by Moon Wizard
Since you are talking about BCEG.Quote:
Originally Posted by SilentRuin
DMGA
REGENA
SAVEA
TREGENA
Are all processed in the same way DMGA and SAVEA do.
Was wrong on the SAVES being processed. It was the SAVEA being processed twice - the 2nd should not be happening for the actual Moonbeam NPC which has an Object named effect. Works when manually dropping the NPC onto the map in range of something with aura. Fails with GAL. Only diff is programmatically creating NPC on top of dire wolf instead of manually dropping it on him from CT.
The IF: !CUSTOM(Object) should have stopped that from processing SAVEA on moonbeam NPC - it for sure did when I dropped it manually.
Is the same code not processing this stuff? (as in drag from CT and drop vs creating the NPC literally in that spot through code?)
I guess I can test by putting the new !self in there.
That would at least prove its not processing the IF on the SAVEA for some reason.
Yep - that is it. Adding the !self prevents it from rolling the SAVEA for the moonbeam NPC. Which implies any IF logic after the AURA but before the SAVEA is being ignored. When the NPC with that moonbeam effect I gave you in DM discord is programmatically created instead of drag dropped from CT.
Unfortunately, that video doesn't exist any longer: "This video isn't available anymore"Quote:
Originally Posted by MrDDT
Another aura effect bug in the new rewritten world of effects. When a CT entry's aura effect is deleted - and it was applying to itself - all other affected CT entries will be removed for their effects but not the local CT entry where it had it applied to itself.
Responded to you in Discord. Not seeing this with just Auras loaded; sent you a video.
Regards,
JPG
Hello there.
I think something is wrong with your recent change to how self-auras work, or I'm missing something obvious here...
In a test 5e campaign with only the Auras extension added, if I add: "AURA: 10; Paladin Effect; SAVE: 10;" to a character, it adds the Paladin Effect to the source of the aura as well. Which, seem to be intended. And when the DM rolls, as expected they get a +10 bonus to the saving throw.
However, when a player makes the roll, it's applying the effect twice for a +20 bonus to the save.
Or, if I add !self to the aura, then the DM rolls, they don't get any bonus as expected. But when the player rolls, they still get a +10 bonus.
Basically, it looks like the effect of the aura is properly blocked for the DM, but not the player.
I'll take a look. Do you have any other extensions running?
Regards,
JPG
Nope, this was tested with just the Auras extension.
Top roll was the GM rolling, bottom roll was the player rolling.
Attachment 67553
@jimlad42,
I just pushed an update that fixed this issue in my local multiplayer testing. Can you please run a new Check for Updates, and try again?
Regards,
JPG