5E - Aura Effects

[MrDDT]

I get the error when I run it with the Aura Effects extension and COP, and a ton others. It all worked up till 10/19 or 10/23 patching, then I got errors... see attachment

Try using this coding, I don't have COP so I can't test it.

Twilight Sanctuary; (C); AURA: 30 color[cyan], !foe; Twilight Sanctuary AoE; TREGENE: 1d6+8

I can break it down a bit for you and others to use more standard coding effects.


; Breaks up coding functions
First part is the name, "Twilight Sancturary"
Second part is effects clauses that might have to do with the effect itself. In this case it's "(C)" for concentration.
Third part is the coding which is "AURA: 30 color[cyan], !foe" which is going to apply an effect.
Fourth Part is the name of effect that is applied from the AURA which you want to name so you know where it's coming from, "Twilight Sancturary AoE"
Fifth part is the applied effect from the AURA coding "TREGENE: 1d6+8"

[MrDDT]

@jfos
So after testing with COP, I was able to ensure that the coding effect I gave above is working 100%.

[jfos]

@jfos
So after testing with COP, I was able to ensure that the coding effect I gave above is working 100%.

100%, confirmed, move that (C) and all is happiness again, TYVM

[SilentRuin]

I meant to mention this a few weeks back - AURA has a bug where when you enter the aura range the selection of the token your dragging is lost on the host. This has vision implications where the only work around is to stop moving the token and reselect it. It would be nice if AURA did not remove the selection as a token moves throught he aura messing up the vision (and probabaly other things).

[MrDDT]

I meant to mention this a few weeks back - AURA has a bug where when you enter the aura range the selection of the token your dragging is lost on the host. This has vision implications where the only work around is to stop moving the token and reselect it. It would be nice if AURA did not remove the selection as a token moves throught he aura messing up the vision (and probabaly other things).

I'm not seeing this issue. Maybe a conflict with an ext? Have you tried causing this to happen in a clean campaign first with no other exts?

[SilentRuin]

I managed to narrow it down to only happen when 3 extensions - AURA, Generic Actions Layers, and Advantages Pointers are in play - never with any two of them - only with all three. As I know I set select to false in two places in Generic Actions Layers I'm going to assume it is the culprit - or will probably never find it - will debug when I get a chance over the next few days.

[SilentRuin]

[I think what I posted about AURA not respecting non targetable things is not true - it simply is not triggering the token onTargetUpdate handler when it targets something. I'm not sure how this happens but as it happens for Advantages - my own stuff. Still not sure how assigning a target can escape this handler in FGU - but it appears it does. I'll have to work out in my own extension to see the why of it before I address this one - if I need to at all. ]

[darrenan]

This extension needs to be updated to work with PFRPG2-Legacy. Add the following to your extension.xml:

<ruleset>
<name>PFRPG2-Legacy</name>
</ruleset>

[SilentRuin]

[I think what I posted about AURA not respecting non targetable things is not true - it simply is not triggering the token onTargetUpdate handler when it targets something. I'm not sure how this happens but as it happens for Advantages - my own stuff. Still not sure how assigning a target can escape this handler in FGU - but it appears it does. I'll have to work out in my own extension to see the why of it before I address this one - if I need to at all. ]

Updated above.

[Desmodaeus]

Just fyi, it is not working for me in 4e. The extension loads but none of the auras function other than showing the text in chat. When I use the older version you linked to however, everything works.