Latest version | 0.9.10 |
---|---|
Minimum Core | 12 |
Compatible Core | 12.331 |
Last updated | 2 months ago |
Created | 1 year ago |
Authors |
|
Languages |
English Русский |
Systems | All systems |
Project source | Project URL |
Read-me | Readme URL |
License | License URL |
This module provides options to calculate how much cover a targeted token has, with respect to a viewer token. Various options are provided to modify how the cover calculation is made. The GM can also define low, medium, and high levels of cover, and associate each level of cover with an active effect that is applied to the targeted token when it has cover. Workflow options are provided to facilitate automation.
This module is closely related to [Alternative Token Visibility](https://github.com/caewok/fvtt-token-visibility). Both rely on the same underlying algorithms to determine whether there are obstacles between the viewer and the target.
Cover Algorithm choices:
- Points. Test whether a 3d ray from a point on the viewer token to a point on the target token is blocked by an obstacle. Multiple points on the target can be tested to determine whether a threshold percentage of rays is met for cover. For overhead tiles, considers them to block unless the ray passes through a transparent portion of the tile.
- Area2d. Test the percentage of the overhead view of a target token that is viewable from the perspective of a point on the viewer token. For overhead tiles, does not consider transparency.
- Area3d. Test the percentage of the 3d view of a target token that is viewable from the perspective of a point on the viewer token. For overhead tiles, uses webGL to test transparency.
Major features:
- Choose whether one or more points on the viewing target are tested for cover, with the best result taken. Options include a "stereo" version that uses two points on the front facing side of the token.
- Adjust viewer and target point locations, shifting from the token border to the center.
- Account for wall height (using the [Wall Height](https://github.com/theripper93/wall-height) module) and overhead tiles.
- Adjust the vision height for tokens and prone tokens.
- For Foundry v12, define a "Set Cover" region behavior
- [libWrapper](https://github.com/ruipin/fvtt-lib-wrapper)
- [socketlib](https://github.com/manuelVo/foundryvtt-socketlib)
- [Alternative Token Visibility](https://github.com/caewok/fvtt-token-visibility). Needed if you want token vision to exactly match token cover.
- [Wall Height](https://github.com/theripper93/wall-height). Not only does Wall Height provide the ability to set elevation for wall tops and bottoms, it also gives tokens height based on their size. The Area3d option for Alt Token Visibility takes full advantage of token height.
- [Elevated Vision](https://github.com/caewok/fvtt-elevated-vision). Can assist with setting terrain and token elevations.
- [Midiqol](https://gitlab.com/tposney/midi-qol). If midiqol is installed, additional options are presented to allow cover calculations during an attack roll.
Consider buying me a beer if you like my work. https://ko-fi.com/caewok
To install this package, open your Foundry Setup screen and navigate to your Module tab and click the Install Module button.
From there, you can either search for the package unique name: tokencover or copy its manifest URL:
And paste it to the input box at the bottom of your window.
You can install this package directly to your Forge account.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Advertisement cookies are used to deliver visitors with customized advertisements based on the pages they visited before and analyze the effectiveness of the ad campaign.