Describe the Problem
Not being able to retrieve and restore FoW data via macros can limit potential enhancements.
The Solution you'd like
Would love to be able to use a function (getFoW(), getTokenFoW(), or getMapFoW() maybe?) to be able to get a snapshot of FoW status (either token or map) so that it could potentially be reloaded later via macros. This would allow elevation or zoned area changes and returns to/from previous areas to "remember" FoW exposure by reloading on demand via macro.
Anyhow, thanks much for considering!
Alternatives that you've considered.
Other solutions to FoW and elevation would probably be a lot more complex, likely requiring a Z dimension instead of just X and Y coordinates.
Additional Context
If @Full Bleed is right, then the FoW data may already exist on a token, so implementation may be fairly straightforward.
Describe the Problem
Not being able to retrieve and restore FoW data via macros can limit potential enhancements.
The Solution you'd like
Would love to be able to use a function (getFoW(), getTokenFoW(), or getMapFoW() maybe?) to be able to get a snapshot of FoW status (either token or map) so that it could potentially be reloaded later via macros. This would allow elevation or zoned area changes and returns to/from previous areas to "remember" FoW exposure by reloading on demand via macro.
Anyhow, thanks much for considering!
Alternatives that you've considered.
Other solutions to FoW and elevation would probably be a lot more complex, likely requiring a Z dimension instead of just X and Y coordinates.
Additional Context
If @Full Bleed is right, then the FoW data may already exist on a token, so implementation may be fairly straightforward.