Grid-Aware Auras

Simply search for 'Grid-Aware Auras' in the Foundry 'Install Module' screen and install it from there.

Alternatively, paste this URL into the 'Manifest URL' field of the 'Install Module' dialog in the Foundry configuration: https://github.com/Wibble199/FoundryVTT-Grid-Aware-Auras/releases/latest/download/module.json, then enable the module in your world.

1. First open a token configuration by using the cog button when right-clicking a token on the scene, or open the prototype token configuration for an actor.
2. Then, navigate to the new "Auras" tab, then click the + button to create a new aura. You can then set the size of the aura, how you want it to appear visually, when it should be visible, and whether you want to add any automation functionality. You can add as many auras as you want!
3. If you need to edit an existing aura, you can click the cog button next to it to edit it. You can also quickly toggle whether that aura is visible by clicking the eye icon.
4. Finally, just click the "Update Token" button.

By default, newly created auras are visible to everyone so long as the token itself is visible. This can be changed in the 'Visibility' tab of the aura's config.

There are some options you can choose from in the dropdown, similar to the Foundry's default "Display Bar" option for token resource bars.

You can also fine-tune the visibility conditions, though this is a little more advanced:

The custom setting enables the checkbox table below the dropdown. This table shows a list of 'states' in the first column, followed by a checkbox for owner and non-owner visibility.

GAA computes visibility by checking which states are applicable, determining whether you are an owner of the token or not, then looking up whether the checkbox is ticked; If so, then the aura is visible. If there are multiple applicable states (for example targeted AND hovered), then the aura will show if ANY of the appliable states are ticked. The so-called 'Default' state is slightly special in that it applies ONLY when there are no other applicable states (i.e. when you are NOT hovering, and NOT targeting, and NOT the token's turn etc.).

In the above example, the aura is visible to a user when that user is hovering the token; OR when the token is selected/controlled (only possible by it's owner); OR if the user owns the token and it is that token's turn in the combat tracker.

Automation is the broad category for doing things when tokens interact with auras. See the documentation for the various automation types offered:

• Effects - For automatically applying or removing active effects to tokens when tokens are inside auras.
• Macros - For running macros when events happen relating to auras.
• Sequencer (If the Sequencer module is installed) - For playing effects on tokens inside an aura.
• Terrain Height Tools (If THT module is installed) - For showing line of sight rulers while dragging tokens.

Note that presets are saved to the Foundry world, meaning that any other players that have permission to update their tokens will be able to add saved presets. You require GM permissions to be able to save, edit, or delete presets however.

To create a preset, you can either open the context menu of an aura that you have already created and choose 'Save as Preset', or you can open the GAA preset manager in Foundry's game settings panel and create a new one from there.

To add a preset to a token or item, click the + button in the aura table and choose the 'Add Preset' item, then choose the preset you wish to add.

You can use the preset manager panel to edit or delete existing presets. Editing a preset will NOT change any cases where this preset has been added to a token/item. Here, you can also choose actor types for the "Auto-apply to" setting. What this does is when tokens that represent an actor of this type are created on the scene, the aura will automatically be added to that token (if an aura with the same name does not already exist).

Note that the enabled/disabled toggle in the preset manager determines the initial enabled/disabled state of the aura. It does not enable or disable the preset itself (i.e. a disabled aura will still show up in the 'Add Preset' menu and will still be auto-applied to relevant tokens).

When dealing with square grids, there are different ways of handling diagonals. You can configure which rules Grid-Aware Auras uses in the module settings. Which one you choose will depend on your game. GAA supports the following:

Name	Picture	Description
Equidistant (1/1/1)		In this ruleset, moving diagonally always costs 1 (i.e. the same as moving horizontally or vertically). Therefore, the resulting aura ends up being a large square around the token. For example, this is how D&D5E usually works.
Alternating (1/2/1)		In this ruleset, the first diagonal costs 1, the second 2, the third 1 again, then 2 again, etc. This is the technique that Pathfinder 2E uses, for example.
Manhattan (2/2/2)		In this ruleset, diagonals are effectly disallowed. Moving 1 square diagonally would always cost 2 (1 horizontal and 1 vertical).
Exact (√2/√2/√2)		Also known as euclidean, this ruleset treats diagonals as √2. This is the same area you would get if you used Foundry's circle template tool with an equivalent radius from the centre of each cell.

(Numbers are for illustrative purposes only)

• Automation Guide
• API Reference
• Hooks
• Custom Aura Target Filters