Allowing tokens to be in a "threshold" position, i.e., in both zones at once

[lektu]

Where should the feature be created?

System

Premium Module

No response

Describe the feature

I play gridless, and a common occurrence in my games is that a character is in zone A, just in the threshold towards zone B (using it as a bit of cover). It is not a matter of "moving one square inside", that'd be meaningless and a bit silly. I don't force them to enter, shoot, and exit. (If they're back inside A, and not in the threshold, then yes, they'd need to move). So currently I have to move the token back and forth if I want the distances to be accurately computed for both zones.

Suggested solution

Supposing there's adjacent zones ABC, and the map is gridless, and a token T is overlapping both A and B, the module would count T as being in A when computing distance to a point in A, but as being in B when computing a distance to B or C. Basically, in each case, it should compute both distances and take the shortest one.

That should be settable, of course, as not everybody would require it. But I think it'd be generally useful for the gridless crowd ;-)

Alternative

No response

Additional context

No response

Validations

• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
• Not a "How To"-question (You can ask questions here: Discussions).

[Cussa]

Hello @lektu ! Thanks for your interesting in the Zone Movement.

I believe that to explain the "issue" (and the possible solution I am releasing right now), I need to share a small technical explanation.

For Gridless maps, we take the distance that is being moved and we split the movement line in small "steps". Then, for each step, we use Foundry's function to check if the token is inside a zone. When we see that the token is inside a zone, we stop this search for the zone. Then we check if it is the same zone that it was on the previous step, and if not, we mark it as a new zone.

Right now, the module is not ready for overlapping movement zones.

Another point to mention is that the path, especially for token movement, is the one Foundry is sending to us, and then we use the Foundry's function to check the path.

I will leave this as open for now and I am asking you to test the new release (1.3.0), which allows you to reduce the "step size", which means that it will break the movement line in more parts. This will increase accuracy, but it may increase calculation time.

If that helps you to solve the problem, let me know and we can close the issue. If not, I will probably ask you for a map example so I can do the tests, and there is a chance that I will need to open an issue on Foundry to see if their function that validates if a point is inside a region is working properly.