Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Add a Rule Element that modifies a token's visibility level for specific types of vision #17666

Open
Icarus-the-phoenix opened this issue Dec 9, 2024 · 0 comments

Comments

@Icarus-the-phoenix
Copy link
Contributor

I've been having an issue where a token with tremorsense can see things it shouldn't be able to see. In the example below I have an Eagle flying 10 ft off the ground behind a wall, but the Cave Worm with tremorsense can still see it.

20241209-2221-18.0732218.mp4

Foundry Core has a solution for this with the Flying Status Effect, but the PF2e system doesn't use Foundry's Core Status Effects in favor of PF2e RAW Conditions (which I agree with). This unfortunately means that tokens can only be hidden from tremorsense by Toggling the the token's visibility to players or setting it as undetected. Which in both cases will prevent any sense from detecting the token. Below is an example of the Flying Status Effect concealing the Eagle from a Purple Worm with tremorsense in DnD5e.

20241209-2235-02.0886306.mp4

For the feature request, it'd be nice to have a Rule Element that allows us to set a token's visibility level (Observed, Hidden, Undetected) for certain types of vision. This could be expanded on later when other senses get added like a precise scent to obfuscate tokens that don't have a scent.

@Icarus-the-phoenix Icarus-the-phoenix changed the title Feature Request: Add a Rule Element that modifies a token's visibility level by specific types of vision Feature Request: Add a Rule Element that modifies a token's visibility level for specific types of vision Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant