-
Notifications
You must be signed in to change notification settings - Fork 5
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
How do i make my module compatible #81
Comments
Which module of yours has the issue? |
The module is question is perceptive more precisely this code |
Short term at least, I am not going to be able to use the default There might be an easy solution for you, though. If you export Hooks.once("init", function() {
game.modules.get(MODULE_ID).api = { PeekingManager };
} Then on my end, I could call something like: const PeekingManager = game.modules.get("perceptive").api.PeekingManager;
PeekingManager.IgnoreWall(wallDoc, objectDoc); |
Thank you, i have added api for that in the newest update, the code for it looks like this: |
I made a change in v0.5.11 that incorporates your api when selecting walls for a |
Thanks for the work, i did a few tests and it almost works. While tokens are visible trough the peeked walls, as intended, the walls shadow doesn't update correctly i.e. the wall still casts a shadow. I dug through your code and found a way to solve this problem by adding this code into the
This still leaves one problem though, since shadows only seem to update correctly once a token moves, i would guess that i would have to update the vision source on my end. Normally |
Try |
Thank you, will try it |
Hello, i was just informed, that a module of mine is not compatible with Elevated Vision. So far the problem seems to be the "ClockwiseSweepPolygon.prototype._testWallInclusion" function. My module adds an additional condition to this (similar to the Wall-Height module). I tried to look through your code but was so far not successful at finding the way Wall-Height is made compatible, so i could not replicate it.
What would be the preferred way to ensure compatibility with Elevated Vision while adding a condition to the "_testWallInclusion" function?
The text was updated successfully, but these errors were encountered: