This PR adds an module settings option to include a token's height attribute (scaled to the scene) to automatically determine if it can see over a wall or not. The following assumptions are made for this calculation:
The tokens used are 3d "cubes" (read: Their width, height, and depth are all equivalent lengths).
The character is able to move their head to their foot level or their head level in order to see under or over a wall, respectively.
Regardless of in-game height, the character represented by the token has some means of peeking over the top of a wall the same "size" as their token (e.g. hopping to see over a wall). This also applies for characters with a "size" nominally smaller than their token, e.g. Small characters in D&D that still use a token with a height of "1".
Potential room for improvement:
Allowing for a config file that maps the token actor's size/in-game height information to an appropriate value, e.g. mapping DnD5e's "sm" size enum to 0.5, an elevation-friendly value.
Creating a Token/PrototypeToken data field for manually setting token height instead
Issue Number
Partially addresses #11, though perhaps not to the specificity of the original poster.
Description
This PR adds an module settings option to include a token's
heightattribute (scaled to the scene) to automatically determine if it can see over a wall or not. The following assumptions are made for this calculation:heightof "1".Potential room for improvement:
"sm"size enum to 0.5, an elevation-friendly value.Issue Number
Partially addresses #11, though perhaps not to the specificity of the original poster.