-
Notifications
You must be signed in to change notification settings - Fork 265
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
GM-Mode FoW autoexpose not working correctly #962
Comments
What is the setting "Auto-expose fog on token movement (GM only)" supposed to do, exactly? According to the wiki:
So according to the wiki at least there is no bug: unowned tokens should not reveal the FoW on personal servers. In any case I suggest we update the tooltip for the setting to make it less ambiguous. |
That preference setting has nothing to do with owned/unowned. Not sure why the wiki has that. Probably got confused with the new Server option. Apparently it is an option that was put in to help with testing map/vbl with only the personal server running. I've never had a clue what it was for before today. Neither the text nor tooltip are particularly helpful so it definitely needs an update to the tooltip. |
Is "Auto-expose fog on token movement (GM only)" suppose to have an effect on personal servers only? If so, maybe it should be renamed to "Auto-expose fog on token movement (personal server only)" |
I've never checked the code to verify it but I believe that is true. |
Based on this discussion I believe the intended effect for GMs is:
|
It use to expose FoW as needed, pretty useful to test VBL. I use to be able to reveal for an owned PC token (I would use a PC token to test) and it no longer works after fixing other FoW issue... I believe it's exposing FoW for the token vs global FoW |
I'm with you so far. :) Note that any fix for this will be pushed to 1.5.9. |
The Wiki error is mine. When I tested the behavior, it wouldn't auto-expose unless I set token ownership - apparently I documented a bug as intended behavior... oops! Have removed the word 'owned' on the Wiki so it is correct once this issue is resolved, and will update it further to reflect any updated tooltip. I'm not sure what a 'Personal Server' is, but I'm using Merudo's comment as a guideline for the updated language.
Will update further with feedback. |
@melek Technically MapTool is always running a server. We refer to the server you have when you just start up MapTool and are working on your campaign, building maps, and so on as a Personal Server. Various internal aspects of MT rely on a server to work. |
The same issue happens with facing - changing the facing while using a cone light source doesn't update the FoW correctly. |
- Fix auto-expose fog on token movement so that tokens expose the fog on personal servers if moved or if their facing is changed - Change text of setting to be clearer - Close RPTools#962
- Fix auto-expose fog on token movement so that tokens expose the fog on personal servers if moved or if their facing is changed - Change text of setting to be clearer - Close RPTools#962
PR #965 fixes this. |
- Fix auto-expose fog on token movement so that tokens expose the fog on personal servers if moved or if their facing is changed - Change text of setting to be clearer - Close RPTools#962
Tested. With setting enabled and no server running, Tokens with vision that are moved now expose FoW. |
Describe the bug
The preferences setting Auto-expose fog on token movement (GM only) stopped working correctly. This setting allows for auto-expose without a server running. With setting enabled, moving tokens are no longer visibly exposing the FoW. It appears that the exposed FoW may be going on the token and not to the global exposed area.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
With that preference setting enabled the Fog should be exposed. This worked in 1.5.4 and was broken with1.5.5. The exposed areas should be part of the global exposed fog.
MapTool Info
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: