5E - Aura Effects

This whole target distance logic is always confusing to me - just posted a bug in FGU for it even...

Gist is - I have a huge thing which means its 15ft wide - or from center to edge 7.5ft then add in whatever aura and... just very hard to figure out. I have that gas cloud and it does not trigger until targeting is 5 ft away because I have set it to aura: 5 - but that is based on targeting distance (FGU code calcs). And with bug shown in post above - it means aura will trigger when I get to 1 grid unit away from that huge tokens border - and if I go 1/2 a grid farther in that causes it to disable the aura because I've gone back to 10ft according to FGU targeting calcs.

It's all quite confusing but explains some very weird things I've been seeing with auras. And of course, any SAVEA type of stuff will actually fail to roll the second half of the effect (damage) when I move out of range even though the saving throw was triggered and rolled. I truly do not understand why an in progress saving throw is somehow truncated simply because the effect was removed. I mean it was in progress - the whole effect string should be processed regardless of the current state of the CT entry itself - you already started processing it and trying to reread the rest of the effect after the roll is looking for trouble.

Distances between two tokens in FGU are found by looking at the closest square of a grid centered around the token based upon the creature size to the target and then "backing up" half a square (and vice versa). For a 5' grid, between two adjacent medium tokens, the two squares will be touching, so bringing each back 2.5', you get a distance of 5'. If there are two squares between a medium and a huge token is 10' for the empty squares and 2.5' for each of the tokens, for 15'.

Attachment 55616

If that huge creatures is emanating an aura of 5', it's going to be emanating 2.5' from every outer square, which would include all adjacent targets, regardless of size. If you started from the middle of the creature, a 5' aura wouldn't affect any creature, which I don't think is what you'd want. Otherwise, a huge creature with a 5' reach would also never be able to make a melee attack against an adjacent creature. Unless I'm missing what the discussion is about...

If you really want a distance from the center of a token and not half a square from the edge, you can pass in the coordinates of the center of the token and not the token itself (I think). In regards to the comment about token height a few posts back - I've confirmed that it matches the calculations of raw FGU in 2 dimensions (of course extending to 3 dimensions if one has a height). If you think it doesn't match the raw calculations, I'd ask that you post the differences on that thread and not imply it's messing you up on this thread.

Quote:

---

Originally Posted by GKEnialb

Distances between two tokens in FGU are found by looking at the closest square of a grid centered around the token based upon the creature size to the target and then "backing up" half a square (and vice versa). For a 5' grid, between two adjacent medium tokens, the two squares will be touching, so bringing each back 2.5', you get a distance of 5'. If there are two squares between a medium and a huge token is 10' for the empty squares and 2.5' for each of the tokens, for 15'.

Attachment 55616

If that huge creatures is emanating an aura of 5', it's going to be emanating 2.5' from every outer square, which would include all adjacent targets, regardless of size. If you started from the middle of the creature, a 5' aura wouldn't affect any creature, which I don't think is what you'd want. Otherwise, a huge creature with a 5' reach would also never be able to make a melee attack against an adjacent creature. Unless I'm missing what the discussion is about...

If you really want a distance from the center of a token and not half a square from the edge, you can pass in the coordinates of the center of the token and not the token itself (I think). In regards to the comment about token height a few posts back - I've confirmed that it matches the calculations of raw FGU in 2 dimensions (of course extending to 3 dimensions if one has a height). If you think it doesn't match the raw calculations, I'd ask that you post the differences on that thread and not imply it's messing you up on this thread.

---

Baring their current bug I mentioned - its just weird. But correct as you state.

For now, until FGU fixes their distance bug I mentioned, I will assign all my minimum auras to 10 ft so they will not flip out when they run into that issue.

Oh, then just working as most game systems dictate range.
Nothing for me to fix there, hooray.

Quote:

---

Originally Posted by bmos

Oh, then just working as most game systems dictate range.
Nothing for me to fix there, hooray.

---

Yeah, I think you're good. If you do decide to go from a point instead of a token, you can use my getTokenWithinShape functions (sphere or cube) in Image instead of Token (or steal the code to use directly in Aura Effects).

(sigh) Another issue - I'm finding that if I have one of the things in range of an aura set invisible - the Token.getDistanceBetween is returning #0 which basically makes the aura ignore that token. Just FYI for some who may have noticed this happening.

Quote:

---

Originally Posted by SilentRuin

(sigh) Another issue - I'm finding that if I have one of the things in range of an aura set invisible - the Token.getDistanceBetween is returning #0 which basically makes the aura ignore that token. Just FYI for some who may have noticed this happening.

---

To clarify, since Invisible is a separate condition that can be set, this is in reference to the state of tokenvis under the actor's combattracker node?

Quote:

---

Originally Posted by bmos

To clarify, since Invisible is a separate condition that can be set, this is in reference to the state of tokenvis under the actor's combattracker node?

---

In reference to the physical token setting of setVisible. If its marked invisible, even though from the host this code runs - it will get a 0 result on distance. In your world, that means any trigger of onChangeEffect that calls that routine where one of the tokens is not visible on the map it will fail to process it (fails your range check).

Keep in mind tokenvis on CT will set the token visibility but setting token visibility will not set the tokenvis in CT - the CT is not a reliable check for map token visibility.

I get an odd reaction with this setup. The Sorcerer (caster) has two auras on:
AURA: 20 ally; REGEN: 4
AURA: 20 !ally; DMGO: 4

her ally gets healed when in range, her enemy gets damaged when in range, all good. But she gets both healed and damaged on her turn. Why?

edit: fixed it with IF: FACTION notself