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

[Bug]: Movement details shown to players for PCs with no vision #4544

Open
kwvanderlinde opened this issue Dec 9, 2023 · 0 comments
Open
Assignees
Labels

Comments

@kwvanderlinde
Copy link
Collaborator

Describe the Bug

If unowned PCs are present on the map with vision, the movement details for a PC are only shown to players when that PC is being moved through the part of the map that tokens can see visible. But if none of the PCs can see (i.e., none of the map is seen by tokens), then the movement details are shown. This is inconsistent, but it also means that the tokens pop into existence while the GM is dragging even though they are not otherwise rendered.

This issue is specific to when Individual FOW is disabled, map vision is not set to Off, and no part of the map is visible to a token.

To Reproduce

  1. Start a server with Individual FOW option disabled.
  2. On a blank map, set vision to Night, and disable fog.
  3. Add two PCs to the map, each with normal or no sight.
  4. Connect to the server with a player client.
  5. As GM, drag one of the PCs.
  6. As the player, watch the dragged PC and its path pop out of nowhere.

Expected Behaviour

If map vision is not Off, token movement should only be shown if in the visible area.

Screenshots

This is the situation described in the reproduction steps:
image
The token is not rendered where it is, but it's path is being rendered.

If we instead have the second PC darkvision, then do the same thing, we see the path stop at the boundary of the vision:
image

MapTool Info

1.14.1

Desktop

Linux Mint 21.2

Additional Context

This looks similar to #4081, but is its polar opposite.

#4081 only applies to Individual FOW and is due to us only checking the visible area and not the exposed fog area. By contrast, this issue only applies to not Individual FOW and is due to us only checking the exposed fog area and not the visible area (in this special case where the visible area is empty).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Needs Testing
Development

No branches or pull requests

1 participant