-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
Collision detection causes tokens to shift from grid #1076
Comments
Hm that's odd, as from what I can see on the picture the center of the token is still to the right of the wall, so it shouldn't even be showing the contents across the wall. Regardless the collision detection should catch this indeed, is this on master or on dev? (or some other branch) |
This is on https://planarally.dice.quest I'm working on getting a local instance set up, and will try it on the dev branch. |
And just to confirm, the "object on the FoW layer that blocks movement" also blocks lighting right? |
Yes, I've got the object blocking both light and movement. |
Do you also have an aura enabled? Because for player tokens, I typically don't have them set to block light or movement because they frequently get players confused, then they can't just drag their player character around over others. This is how a typical PC looks for me And the results are like this with a proper map mask. Screencast.from.2022-12-17.10-31-13.webm |
My original question was regarding the wall, not the player token. The bug here is related to clipping through the wall somehow. I haven't been able to reproduce this easily myself yet, which is why this is not resolved yet. |
Sometimes, when a player moves close to an object on the FoW layer that blocks movement, imprecise collision detection permits the token to move half-way into the area that's blocked. Not only does the player's aura expose some hidden material (in an adjacent room, for instance) but it also causes the player's token to be knocked out of grid alignment.
The text was updated successfully, but these errors were encountered: