AoE Effects

[bwatford]

Ok the fix for the Forge issue with AoE Effects has been handled.
According to MW we have to change the name of the file itself back to FG-Aura-Effect.ext to get the updater in Forge to work properly and update everyone correctly. This has already been done.

If you grabbed this extension already, just delete the "AoE Effects.ext" from your extensions folder and reupdate. The name will still appear as AoE Effects in the extensions list.

[bwatford]

Indeed, it's fixed and it works now, thanks.

The Forge page mentions this:

I can't find that setting in the Options window though, where is it available?

This has been removed from the Forge page as Aura's are silent by default now and a GM option was no longer needed.

[SilentRuin]

Thanks for that list @SilentRuin, that is very helpful.

We are already hard at work, on correcting the "cube" issue that is present in the extension that was left over from the old Aura Effects coding.

The logic that we will be using for version 2 of this extension will address the issue and make cubes, well cubes (3 dimensional), and squares will be flat.

- default will stay sphere (3d)
- circle (flat, no height)
- cylinder (3d)
- square (flat, no height)
- cube (3d)
- wall (3d)
- Line (flat, no height)

But that is down the road a bit, trying to get beyond the version 1 release at the moment.

Beware of changing legacy syntax - nobody wants to go in an update all their old syntax for the sake of "making sense". Just FYI. Causing that level of disruption would be like...

Well an FG update breaking the world

[MrDDT]

Beware of changing legacy syntax - nobody wants to go in an update all their old syntax for the sake of "making sense". Just FYI. Causing that level of disruption would be like...

Well an FG update breaking the world

I agree with your premise however, cube should have always been just that, the fact it wasn't is an issue. So more of a bug fix on this one.

All the other changes are adds and not going to affect anyone's old coding.


For the record for anyone wondering my settings on detection.

-.1 "Aura Size Adjustment"
Near Edge "Percent Token Overlap"
100% of grid "Token: Auto-scale to grid" (this is in Token options)
Default "Map: Diagonal distance" (this is in House rules"
Snap to Grid (this is on each image)

This gives me near perfect triggering as soon as any creature steps a toe inside the AOE areas.

[bwatford]

For the record for anyone wondering my settings on detection.

-.1 "Aura Size Adjustment"
Near Edge "Percent Token Overlap"
100% of grid "Token: Auto-scale to grid" (this is in Token options)
Default "Map: Diagonal distance" (this is in House rules"
Snap to Grid (this is on each image)

This gives me near perfect triggering as soon as any creature steps a toe inside the AOE areas.

Exactly what the new settings were made for, each GM can have their own desired triggering points for Aura's.

Here's mine, this gives me the closest to the 5e 2024 rule that a Aura/Emanation needs to cover @ half of a square for it to be affected by the aura. It is not exactly perfect, as larger creature (3x3, and 4x4) need to be in the Aura a bit further but close enough to match what users expect from the rules.

0 "Aura Size Adjustment"
Quarter "Percent Token Overlap"
80% of grid "Token: Auto-scale to grid" (this is in Token options)
1.5x "Map: Diagonal distance" (this is in House rules") This is, so weapons/spells compute correct distance at range. I still let my players treat every square as 5 feet when moving.
Snap to Grid (this is on each image)

[SilentRuin]

Exactly what the new settings were made for, each GM can have their own desired triggering points for Aura's.

Here's mine, this gives me the closest to the 5e 2024 rule that a Aura/Emanation needs to cover @ half of a square for it to be affected by the aura. It is not exactly perfect, as larger creature (3x3, and 4x4) need to be in the Aura a bit further but close enough to match what users expect from the rules.

0 "Aura Size Adjustment"
Quarter "Percent Token Overlap"
80% of grid "Token: Auto-scale to grid" (this is in Token options)
1.5x "Map: Diagonal distance" (this is in House rules") This is, so weapons/spells compute correct distance at range. I still let my players treat every square as 5 feet when moving.
Snap to Grid (this is on each image)

Bah! All right thinking people only use 2014 5E and only with

0 "Aura Size Adjustment"
Near Edge "Percent Token Overlap"
80% of grid "Token: Auto-scale to grid" (this is in Token options)
RAW "Map: Diagonal distance" (this is in House rules") TRUE DISTANCE RULES!
NO Snap to Grid (this is on each image) FREE MOVEMENT RULES!

Is the ONLY way!!!!

[SilentRuin]

Updated some more things I define in my GAL campaigns - also described the current arguments in detail though bwatford should probably turn this into readable English once he delivers the latest 3drect <*prefix> paramB support. Anyway, that's enough for me my dragonborn players both now have their breath weapon automation...

https://www.fantasygrounds.com/forum...l=1#post765159


Obviously this is just unseen area - you get no graphics with just AURA - just the AOE effect triggers.
************
AURA: <paramA> ..., <Shape keyword>, point...

point - keyword indicating shape will have paramA starting at center of source token, if not defined it defaults to paramA = <paramA> + token distance from center to edge (various things can effect this distance). Any mention of paramA below will assume this is already taken into account to keep things simple. The same is true for any other distance parameters that need to have their length adjusted in the same manner. Auras placed on object NPCs (all of GAL stuff) typically have point defined. Things placed on a PC/NPC like aura of courage, etc. usually start from the edge of that token instead of the center so do not have point defined (default behavior).

<Shape keyword>

None recognized

Defaults to Sphere shape with paramA radius.
Example: Below will trigger on all tokens 10 ft from center of source token this effect is on.

...; AURA: 10 all, point; ...

cylinder|<paramB>|<paramC>|<paramD>|

paramA = radius of cylinder
<paramB> = z min - if z min or zmax are not defined defaults to 0
<paramC> = z max - if z min or zmax are not defined defaults to 0
<paramD> = 2nd cylinder radius to form two bounding cylinders where triggers occur between them (note if this 2nd radius is defined the software will determine which radius is the outer radius and which is the inner radius based on length)
Example: Below will trigger on all tokens within 10 ft from center of source token this effect is on and between the zmin of 0 and zmax of 10

...; AURA: 10 all, cylinder|0|10, point; ...

Example: Below will trigger on all tokens between 10 and 20 ft from center of source token this effect is on and between zmin of 0 and zmax of 10

...; AURA: 10 all, cylinder|0|10|20, point; ...

3drect|<* prefix><paramB>|<paramC>|<paramD>|<paramE>

paramA = length of rectangle (extending out along xy plane orientation)
paramB = width of rectangle defaulted to paramA if not defined. The rectangle is placed with center point the same as the center point of the source token. Unless the <* prefix> is in front of the numeric paramB - then it will move the center point of the rectangle so that the base is against the center or edge of token as the point option dictated.
paramC = z min - if z min or zmax are not defined defaults to 0
paramD = z max - if z min or zmax are not defined defaults to 0
paramE = orientation in degrees of the rectangle. If not defined will be the orientation of the source token at run time.
Example: Below will trigger on all tokens within the bounds of a 10 ft square centered on the source token center point and oriented to the source tokens orientation on the xy plane of the map

...; AURA: 10 all, 3drect, point; ...

Example: Below will trigger on all tokens within the bounds of a 10 ft square centered on the source token center point and oriented along the x axis in a positive direction

...; AURA: 10 all, 3drect|10|0|0|0, point; ...

Example: Below will trigger on all tokens within a 10 ft cube centered on the source token center point and oriented to the source tokens orientation on the xy plane of the map

...; AURA: 10 all, 3drect|10|0|10, point; ...

Example: Below will trigger on all tokens within a 10 ft orthogonal cube centered on the source token center point and oriented along the x axis in a positive direction

...; AURA: 10 all, 3drect|10|0|10|0, point; ...

Example: Below will trigger on all tokens within 60x5ft rectangle centered on the source token center point between zmin of 0 and zmax of 10 and and oriented to the source tokens orientation on the xy plane of the map

...; AURA: 60 all, 3drect|5|0|10, point; ...

Example: Below will trigger on all tokens within 30x5ft rectangle projected out from the source token center point so that the base of rectangle is touching the center point of the source token between zmin of 0 and zmax of 10 and and oriented to the source tokens orientation on the xy plane of the map

...; AURA: 30 all, 3drect|*5|0|10, point; ...

cone

paramA = height of cone (extending out along xy plane orientation)
paramB = orientation in degrees of the cone. If not defined will be the orientation of the source token at run time. (can't see this ever being set)
paramC = half angle of cone defaulted to 26.5 which matches FG pointer shape cone (can't see this ever being set)
Example: Below will trigger on all tokens within 15ft cone starting at edge of the token and oriented to the source tokens orientation on the xy plane of the map with a 26.5 degree half angle matching that of the pointer shape cone used in FG.

...; AURA: 15 all, cone; ...

************

With GAL I use for my active campaign and my two dragonborn players tested breath weapons

[bwatford]

I will include the changes for SilentRuin in the small update dropping next week v1.1.

Which will also merge the "Aura's Visualized" extension into the core code of AoE Effects and have some built in examples of how area of effect graphics can be easily added to Aura areas in your game with a drag and drop interface. There will be a video example of the option when it becomes available for all next week but I think everybody is going to find it is really cool to have built in animated spirt guardian aura's on the table, and the ability to customize your own auras however you like.

[Moon Wizard]

Ping me when the integration with Auras Visualized is Live, and I can retire the Auras Visualized forge item.

Regards,
JPG

[Tronic]

I can't seem to exclude enemy characters from the Aura effects I am creating. Every character on the map seems to get the aura regardless of faction (Friend, Hostile, Neutral).
Here is an example of what I was trying:
AC Boost; AURA: 10 ally; AC Boost; AC: 6

I am using the PFRPG ruleset. Any ideas? I already tried deleting the extension from my PC, and then re-updating.