Dynamic Lighting - Player tokens not saving vision toggle on/off

Hi Everyone, today I spent 2 hours by trying to apply some vision changes to characters in the journal without success. My friend has set up a jumpgate game with Dynamic Lighting and I as a DM of that game am trying to switch off the vision toggle for a character. It works for the token of the character but not for the character in the journal. I am able to apply a lot of other changes as default setting to the linked character in the journal, such as changing the token size or activate/deatoivate night vision. But deactivating vision at all won't stick. Whenever I drag a character from the jounral to the VDT, the vision toggle will be switched on again. So, why am I able to switch of night vision but not vision? Is that something about the default setting of the game? Thanks!

Hi Der Arkanier,  Make sure that after you adjust the token you update that token to the Character.  If you are doing that and still have an issue please PM me an invite and I can see what might be going on. 

Gauss said: Hi Der Arkanier,  Make sure that after you adjust the token you update that token to the Character.  If you are doing that and still have an issue please PM me an invite and I can see what might be going on.  Hi Gauss, yes, I made sure to update the token to the character. I also opened the character in the journal and edited token properties in the character window but after pressing save, closing and opening the character again, the toggle was back to "vision on". I will follow up by PM.

Does your friend (the game creator) have a Plus subscription or a Pro subscription?  If they have a Pro subscription, then I'm guessing that the game has a script running that is overriding your settings and automatically applying vision to tokens that have a player as controller. Aura/Tint Healthcolors is notorious for doing this for things like token nameplates and auras (I don't think it adjusts vision) as an example. Can you list the scripts that are being used in the game or post a screenshot of the script settings page? You may need to have the game creator do that for you - I don't think promoted co-GMs have access to the script settings page.

To my knowledge it is only a Plus subscription, not a Pro subscription.  I have 0 experience with scripts.  Is it possible that a baked in script is doing that nevertheless? Or maybe the defult settings that the game creator chose for the game can prevent a player controlled chacrater's vision from being toggled off?

Is the token linked to the correct character sheet?  Is there more than one character with the same name? Double check the Journal for duplicates, as well as any that might be archived. What can happen is this: the token for "Bob" is linked to "Carl".  You change the vision off and update the default token, but it updates the "Carl" character, so when you pull "Bob" out of the Journal, it still shows up with vision on, because "Bob" was never actually updated. It's the same thing if you have two characters named "Bob".  You are linked to the 2nd "Bob", but you are pulling out the first "Bob", and that sheet's default token is never being updated.

Yes, it is linked correctly. I also tried a different procedure and just created a new character for that purpose, called it test light effect. Then I did not drag it onto the VDT but opened it in the journal, clicked on token properties, switched of vision on the Lighting Tab, pressed the "save changes" button and opened tha settings again. The vision toggle is always back on. Next, I tried the other approach and dragged the new character from the journal onto the desktop. There I updated the token settings and set the toggle to "vision Off" and saved the token. This setting for the token always sticks. But when I update the respective character by clicking the "update default token" button in the Token's settings and then press "open character sheet" to double check or just drag the supposed to be updated character from the journal onto the VDT a second time, "vision" in the character settings or in the settings of the second token on the VDT remains always switched on. But I understand that not being the creator of the game has its limits and it is difficult for you guys to help me. So,I will check with him first before circling back to you again. It might take 2 weeks because we both are busy with work atm. Thanks for your efforts so far.  

I can give an update on this matter. The game creator of the game in question changed the default settings to token vision off and now it works like a charm. Even better: Severeal character specific visions settings, such as granting night vision to characters were not overwritten by the new game default settings. So, we dont have to change all characters that were already set up for niught vision.  Still, I wonder whether to address a ticket on that matter as I guess that a character specific token vision settings should be able to overwrite general game wide token vision settings.  It looks as if the default settings can be permanently overwritten by activating "vision" on characters if the game default is "off". But If the game default was "Vision on", it vould not be toggled off on a character. But maybe that is working as intended and it's just me strugglng with that problem. However, thanks for your support!

FYI, setting token defaults only affects new tokens, not tokens already in play. Also, I still suspect something else was going in in that game. A default of vision on (again, the campaign defaults should only affect newly created tokens) should not toggle an existing token. I'm not at my regular computer right now, but when I get a chance, I'll try to replicate your third method above and see if I can verify that there is a bug with those specific steps (editing the token, saving defaults, and then using the open sheet button while the token edit window is still open might be bugged.)

OK, I have run some tests. In my regular game, if I set defaults on the token settings and press "Update Token", those changes ARE NOT reflected in the next default token dragged out from the journal tab. This is in agreement with the problem you are experiencing. This is a very large game with a metric ton of mods, though I don't think any of them should affect this behavior. In a brand new game, if I set defaults on the token settings and press "Update Token", those changes ARE reflected in the next default token dragged out from the journal tab. This is the expected behavior. So something is going on here, either due to the size of the game (might be a timing issue), or it might be due to a mod's interference. In either case, opening the character sheet in edit mode and updating the token from there always works. This is the method I typically use, or I use Token-mod's update default token command. they seem to be reliable. "Update Token" from the token settings panel seems to be less reliable, due to some unknown factor. I'll report this and see if there is any insight.

Further information: In my regular game, deliberately crashing the API causes the "Update Token" button in the token settings to behave properly. Either there is an interfering script, or something about the nature of an open and running sandbox disturbs the process. I have decided not to file a report in this case, since the issue seems to deal with a local setup (i.e. some script action). If you wish to file a report of your own, you can use a  Help Center Request . Be sure to include thorough reproduction steps, and link them to this thread for full info, including steps I and the others have made or suggested. In the meantime, updating the token defaults through the character sheet edit settings seems to be more reliable.

Thanks for looking into this. Just to clarify and to avoid potential confusion: The trouble not being able to update character settings: 1) was limited to dynamic lighting settings. I still was able to e.g. change token sizes or add auras and update the related character 2) When I had the problem, it occured on all routes: When I updated settings from the character window or on the token window. I was never able to update the character. But when I updated just the toke non the VDD, the changes were reflected on the token only.&nbsp; 3) We did not solve it by starting a new game but by changing defults in an existing game. I cannot report how exactly but the game creator did it but he just followed that guide:&nbsp; <a href="https://help.roll20.net/hc/en-us/articles/360053106074-Default-Settings-For-Dynamic-Lighting#h_01H9FSKPBPYPPX9GFPBCXERY4Y" rel="nofollow">https://help.roll20.net/hc/en-us/articles/360053106074-Default-Settings-For-Dynamic-Lighting#h_01H9FSKPBPYPPX9GFPBCXERY4Y</a> Having done that fix, I now can update the vision settings for a character from the token settings window or from the character settings window either way and also the cross refrence&nbsp; updates from character to all tokens and from a token to the respective character work.&nbsp;&nbsp; I cannot give a better analysis, since I was not with him, when he fixed the problem.

keithcurtis said: Further information: In my regular game, deliberately crashing the API causes the "Update Token" button in the token settings to behave properly. Either there is an interfering script, or something about the nature of an open and running sandbox disturbs the process. I have decided not to file a report in this case, since the issue seems to deal with a local setup (i.e. some script action). If you wish to file a report of your own, you can use a&nbsp; Help Center Request . Be sure to include thorough reproduction steps, and link them to this thread for full info, including steps I and the others have made or suggested. In the meantime, updating the token defaults through the character sheet edit settings seems to be more reliable. Thanks so much. Your analysis goes far beyond my understanding. We are not using scripts (not intentionally at least) and don't have a pro account. We were able to solve the problem by applying the guide, I just posted. As we are even unexperienced in jump gate and were playing around with lighing settings before, we might have caused some kind of hickup that seems to be solved by having the default settings for that game changed. I will not file a report until that problem pops up again. Thanks for all your efforts!