5E - Aura Effects

[GKEnialb]

SilentRuin and I identified the new incompatibility with Token Height (not automatically updating the aura when height is changed until you move the token) and a fix for it. Token Height has a new version on the Forge with the fix, though needs to have a new version of Aura Effects pushed as well (to make notifyTokenMove global).

[SilentRuin]

SilentRuin and I identified the new incompatibility with Token Height (not automatically updating the aura when height is changed until you move the token) and a fix for it. Token Height has a new version on the Forge with the fix, though needs to have a new version of Aura Effects pushed as well (to make notifyTokenMove global).

Not sure when bmos will get back to it as its the holidays but he has the fixes to expose the routine you needed and also to fix the auras interacting with tokens in other images (but in same map coords). He will let you know when he gets around to all this.

[bmos]

Thanks for that.

Aura Effect v1.21
* Restructured a bunch of code
* Added trigger for when adding creatures to the map during a battle. Resolved issue #17.
* Found an issue with Faction checks which is now fixed. In some cases, the wrong actor was being checked resulting in auras being added/removed incorrectly.
* Limited processing to actors that have tokens on the same map
* Add !self and ~self as an alternative to notself for logical consistency. self, however, is not supported.
* Allow use of decimal places in aura range
Click here to see raw code changes

I'm having an issue where when one of my players attempts to apply the Hex disadvantage condition to a creature, I'm getting an error popping up in the console. I have narrowed it down to something about the Aura of Protection that is being adding when the PC is added to the CT. If the Aura is active on the PCs effect list in the CT, and the Hex condition is applied I get the error. If I then remove the Aura of Protection, and apply the Hex condition, it works as intended.

Basically, if the Aura is active on the player, before the Hex is added to the creature, then I get the error.

Can you re-test this with the latest update and let me know if it's still happening?

[GKEnialb]

And Token Height and Aura Effects are back to working together seamlessly!

[SilentRuin]

Thanks for that.

Aura Effect v1.21
* Restructured a bunch of code
* Added trigger for when adding creatures to the map during a battle. Resolved issue #17.
* Found an issue with Faction checks which is now fixed. In some cases, the wrong actor was being checked resulting in auras being added/removed incorrectly.
* Limited processing to actors that have tokens on the same map
* Add !self and ~self as an alternative to notself for logical consistency. self, however, is not supported.
Click here to see raw code changes

Can you re-test this with the latest update and let me know if it's still happening?

Redacted

[SilentRuin]

Turns out it was the new foe logic that did me in. I had a bunch of

AURA: 15 foe

in my effects which really now need to be

AURA: 15 !ally

[bmos]

In case it helps anyone else struggling with replacing auras in their modules after the recent change, here is a regex replacement that should make old effects work a lot better.

If run on a file last used before v1.20:
It will make auras that previously targeted actors whose faction matches the source again do the same.
It will make auras that previously targeted actors whose faction does not match the source again do the same.
Likely some auras will still need further adjustment and they can be optimized and shortened much better now if rewritten, but it might help someone.
Obviously make sure you have a backup before doing text replacement on any files!

Notepad++
AURA ([0-9.]+) friend; -> AURA \1 ally;
AURA ([0-9.]+) foe; -> AURA \1 !ally;

Standard
AURA ([0-9.]+) friend; -> AURA $& ally;
AURA ([0-9.]+) foe; -> AURA $& !ally;

[ZelieDad]

With everything happening with the new version, should I just wait until it settles down, or I am good to retest?

[ColoradoGM]

I'm not clear on the difference between friend and ally. If there are 4 factions (green/PC, red/ hostile, yellow/neutral, and white/"faction"), and I'm green, is there anyone who is friend but not ally, or vice versa? If I'm red, does that change?

[MrDDT]

I'm not clear on the difference between friend and ally. If there are 4 factions (green/PC, red/ hostile, yellow/neutral, and white/"faction"), and I'm green, is there anyone who is friend but not ally, or vice versa? If I'm red, does that change?

If you want it to be exactly like before just change anything that was set to foe to !ally, and anything set to friend to be ally

The same faction types as above are available, along with "notself":

all - does not block processing on any actor
friend - continues if the effect bearer's faction is "friend"
foe - continues if the effect bearer's faction is "foe"
neutral - continues if the effect bearer's faction is "neutral"
faction - continues if the effect bearer's faction is blank
ally - continues if the effect bearer's faction matches the effect source's faction
enemy - continues if the effect bearer's faction is "foe" and the effect source's faction is "friend" (or vice versa)
notself - continues if the effect bearer does not match the effect source's

Also note that if you want everyone other than your enemy, you would do !enemy now, which is useful for some stuff too.
This would include all factions other than the opposing faction from you. So if you were marked as foe, then only green would NOT be included in this.

Let me know if that helps.