It fixed it! Thanks!
Printable View
https://www.fantasygrounds.com/forum...l=1#post592655
I'm not the OP so I can't update the first post. I'd recommend reading the thread for updates and checking my github page periodically if you are interested in builds that I put together.
Thanks for the update! I can confirm that the "effect already exists" messages are gone (along with adding the effect multiple times), but I still get a bunch of "Unable to find effect to remove" in the DM's chat when a player with an aura moves towards the targets and the DM accepts it (moving from outside the range to several squares inside the range).
Attachment 45595
The aura I'm using for that test is:
Quote:
AURA: 20 foe; Storm Sphere; IF: FACTION(all); SAVEO: Strength DC 17 (M)(H); SAVEDMG: 2d6 bludgeoning (C)
I don't know anything about FGU's token system so fixing that stuff might take me a bit. I've noted it in my issue tracker and will post a new build when I have made enough progress.
I'm also hoping to make it add resulting effects as soon as the effect is added (without requiring the token to be moved or the window to be closed and re-opened).
Aura Effect v0.6
* adding an AURA effect will now add FROMAURA effects based on current token positions
* fix FROMAURA effects not being removed when 'parent' AURA effects is removed
* code cleanup and use of more local functions
for future builds from me, watch the thread in my signature
Does this also work with FGU? I did not read through the 20 some pages of posts.
It seems this is conflicting with GKEnialb's 5E - Token Height Indicator extension (at least v1.7 and greater).
As soon as you move into the aura area FGU locks up. Frozen. Never seen that before. I (and others) have posted on his thread too but I thought I stop by here to give a heads up.
Cool. Thank you.
Can anyone help me with this?
I'm trying to code Entangle spell.
I've added on the map a token for this spell and i'm using this code:
AURA: 20 foe; Restrained; SAVEEND: STR DC 13 (C)
My intent is: When there's a foe in a 20 feet radius of the spell token, the character should be "Restrained". At the End of its Turn, it can make a STR DC 13 Check to ende the effect.
Everything is working, except the Restrained Part. The caracter isn't GRANTADVATK nor DISATK when i attack with it.
EDIT: Nevermind, i fixed with: AURA: 20 foe; restrained; Restrained; SAVEEND: STR DC 13 (C)
Good question. It seems that the aura needs a name in the formula.
So it could be:
AURA: 20 foe; Entangle; Restrained; SAVEEND: STR DC 13; (C)
But i don't know for sure.
And using the ‘Entangle’ label that Henrique shows would be the best option as it tells everyone why the target is restrained.
Another question. Is there an option to capture savedc automatically?
I tried to use SAVEEND: STR DC WIS+8+PRF but it didn't work
You should ask that question over here. This extension just does the AURAs, not the saves.
However, try SAVEEND: STR DC 8 [WIS] [PRF]. If this was a normal FG bonus like a strength bonus (STR: 8 [WIS] [PRF]), that would be how you could write that. I don't know if that extension uses the same logic/pattern.
not sure what PRF is though (we don't have that in pathfinder), so that might not work
EDIT: added space between [WIS] and [PRF] because otherwise it doesn't work
PRF is standard for Proficiency bonus for D&D according to the FG wiki. Thanks gonna try that
Attachment 45703
The error only occurs when using Polymorph specifically (IE not wild shape, shapechange etc). The errors are here.
The combat manager Lua error appears when the concentration effect for polymorph is removed. The polymorphism.lua error happens when an NPC uses polymorph. It looks like the polymorphism.lua issue is just polymorphism as I'm getting that with it alone, but the first error only occurs with aura effects.
So I'm seeing something weird, when using the Spirit Guardians coding listed in post #1, the caster is taking damage on their turn. The enemies are getting it as well, but each turn for the caster, they are being damaged by the effect as well.
AURA: 15 foe; Spirit Guardians; IF: FACTION(foe); SAVEO: wisdom DC 17 (M)(H); SAVEDMG: 3d8 necrotic; (C)
So, I have not had a case where I had these situations. I did load a test environment and I can confirm both and as you describe. One is with the poly ext and the other is when auras are on with poly (and ending concentration).
[4/14/2021 10:01:30 PM] RULESET: Dungeons and Dragons (5E) ruleset (v2021-04-13) for Fantasy Grounds
Copyright 2021 Smiteworks USA, LLC
[4/14/2021 10:01:30 PM] RULESET: Core RPG ruleset (v2021-04-14) for Fantasy Grounds
Copyright 2021 Smiteworks USA, LLC
[4/14/2021 10:01:30 PM] EXTENSION: Roboto Font Extension v1.1
[4/14/2021 10:01:30 PM] EXTENSION: Polymorphism v1.16 for Fantasy Grounds Unity \rCopyright 2021 SilentRuin \rAllow PC/NPC sheet to turn into another NPC and back again following the various polymorph spell requirements.
[4/14/2021 10:01:30 PM] EXTENSION: Aura Effects - Extension v0.6\r--by Kent McCullough 2020 updated by bmos
[4/14/2021 10:01:30 PM] MEASURE: LOAD - PART 2 - 17.343845
[4/14/2021 10:01:34 PM] [WARNING] buttoncontrol: Could not find normal icon () in control (toggle_unmask) in class (imagewindow_toolbar)
[4/14/2021 10:01:39 PM] [WARNING] Frame tabs contains out-of-range values in BottomLeft.
[4/14/2021 10:01:42 PM] [ERROR] Handler error: [string "scripts/manager_combat.lua"]:98: attempt to index local 'nodeEffectList' (a userdata value)
I haven't tested how FACTION works very much (I'm not running any games at the moment), but I think it works inverse to the aura type. It seems AURA type uses the terms "friend" and "foe" in the sense of hostility to the person bearing the AURA effect. The FACTION check, however, seems to be based on the faction entry in the combat tracker.
I will not be able to fix the polymorph compatibility issue as it is a paid extension and the script error is being created by SilenRuin's scripts.
They can address it in their extension or can reach out to me to provide information on what the code their is doing (if it needs to be changed here).
Also here is a re-post of my latest release in case people have a hard time finding it:
I figured that was the case. I really am just documenting the issue in case someone was able to fix it in the future. The up side is that it seems to work even though it throws the error. I have no idea if something else is broken beyond that.
Edit: I see you have already reached out. I think you may have better luck than me as you have a better sense of what the root cause is. Thanks!
I replied to your comment in my thread here.
Yeah, based on my current understanding of what is happening, that's not likely to get fixed.
Improving compatibility with paid extensions for rulesets I don't use is a pretty low priority, although if someone fixes it and shares the fix with me I'll probably include it here.