Default terrains for dnd5e

Add json folder to workflow so default dnd5e terrains are present.

Full Changelog: 0.3.2...0.3.3

Elevation Ruler compatibility

Address compatibility with Elevation Ruler. Requires Elevation Ruler v0.9.5.

Full Changelog: 0.3.1...0.3.2

Remove `socketlib` dependency

Remove the dependency on socketslib. Instead use firstGM test for setting terrain. Fixes duplicative terrain getting set when users enter region.

Full Changelog: 0.3.0...0.3.1

Regions!

Uses the Foundry v12 Region system.
Substantial re-write of the module.
Provides two region behaviors: setTerrain and setElevation. Region behaviors trigger active effects on actors as they pass through regions.
Enhanced region drawing tools provided: fill by grid squares, fill by line-of-sight, and fill enclosed walls. Fill by grid squares and fill enclosed walls both are capable of constructing region shapes with holes.
Some default terrains provided for dnd5e and pf2e.

Full Changelog: 0.2.0...0.3.0

Foundry v12

Initial Foundry v12 compatibility.
Additional releases (starting with v0.3.0) will focus on transitioning to using the Region system in v12. Version 0.2 series is completely separate from Regions and is intended as a stop-gap.

Full Changelog: 0.1.5...0.2.0

Fix for newer dnd5e v3

0.1.5

Fix error when applying terrain effects. (Should now work with dnd5e 3.x updates.)

Add a setting to choose whether to display the terrain icon when applying terrain effects to tokens.

Full Changelog: 0.1.4...0.1.5

Bug fix for Elevation Ruler with Elevated Vision

Fix error when using Elevated Vision and Elevation Ruler along with Terrain Mapper and the token moves over a terrain.

Update lib geometry to v0.2.18.

Full Changelog: 0.1.3...0.1.4

Bug fixes for Elevation Ruler

Bug fixes related to calculating movement penalty; added ability to calculate movement penalty for a given shape.
Fix for tile cache not updating.
Move PixelCache to lib geometry.
Fix for updating settings cache.
Update lib geometry to v0.2.17.

Full Changelog: 0.1.2...0.1.3

Compatibility with Elevation Ruler

Improvements to calculating movement penalty across a path for compatibility with Elevation Ruler:

• Change Terrain.percentMovementForTokenAlongPath to return the movement penalty, not the movement percent applied to the token. So if the token is at 50% movement speed for a given terrain, this would return 1.5 for a path completely in the terrain. Necessary so the averaging across different terrains works properly.

• Force a measurement for terrain and elevation at the beginning and end of a path in instances when it would otherwise be omitted. Necessary to capture when t=0 or t=1 rounds to somewhere other than the exact origin point or destination point, respectively.

Full Changelog: 0.1.1...0.1.2

Bug fix re Set map errors

Fix errors related to Set map modifications. Closes issue #21. Thanks @AterIgnis for the code suggestion!
Fix pixelCache not initialized error.