Token auto updates Nameplate and Vision

Every time I change a token's settings for Nameplate and Vision to off it doesn't remember them or overrides them to back on again. This occurs after I have edited and saved the token to the character but when I pull a fresh one out from the Journal they are back on again. If I change the game default settings for both Nameplate and Vision to off I can save a token with those settings off or on. But with those two defaults on I cannot save a token with them off, they simply are turned on again. I would prefer to have Nameplate and Vision on as it is less work to set up every new monster or creature. Any insights would be appreciated. I just wanted a torch that couldn't see or says "Torch" under it. Steps Taken Game Default Settings for Nameplate and Vision turned on Create new character Add artwork Drag new token to page Edit token to Nameplate off, Vision off, Bright and low light on to 20 feet Save Changes Save token to character by clicking Use Selected Token Save changes Drag new token out from Journal Expected Result: Token has no Vision or Nameplate End Result: Token has Vision and Nameplate Tech Specs D&D 5e, a Jumpgate game allowing both 2014 and 2024 Chrome says it is up-to-date and I cleared my cache, problem persists. I have no scripts installed, I removed the one I had (Dungeon Alchemist) and the problem persists.

Hi Ben Rohl,&nbsp; First, I strongly suggest turning Vision off in your Game Default Settings. It should not be turned on because it can use a ton of resources for the GM. PCs don't need it turned on since PCs are a minority and can be turned on manually.&nbsp; Put another way: unless you want every single image in your game, including map images, to have a setting, don't turn it on in the Game Defaults.&nbsp; As for the problem you are having, there is an intermittent issue where the Game Default Settings can override the settings. The best suggestion I have is in that case disable the setting, Apply Default Settings, and turn them on manually.&nbsp; Sometimes you can get the system to get aligned correctly but it takes a bunch of back and forth between Game Default Settings and Apply Default Settings.&nbsp; I also suggest filing a bug report via the Help Center.&nbsp; <a href="https://help.roll20.net/hc/en-us/requests/new" rel="nofollow">https://help.roll20.net/hc/en-us/requests/new</a>

Thank you for the very quick reply! I'll go ahead and turn off Vision (didn't think of it being resource intensive but makes sense) and get to applying new defaults. Again, thank you Gauss!

I have been told by the dev team that multiple tokens with sight on is no longer the resource and performance issue it once was. True or not (this was years ago when the Dynamic Lighting system was overhauled), there is another, more immediate issue. For the GM, every character with sight displays what they see. And it's multiplicative. Ten goblins with darkvision can make a small unlit room seem like it is blazing with light. This leads to confusion and false impressions, particularly in published adventures, where the GM is not the one who set up the Dynamic Lighting.

I agree it is no longer the issue it once was, but still in the last year I've fielded a few reports from users where there was still a performance hit. Pretty significant in one user's case.&nbsp;

Yeah, that's why I couched the claim with (true or not). Code behavior changes over time. The multiplicative vision issue is the reason why adventures are created the way they are: all vision/darkvision settings set, but not activated. that way, whenever a GM turns on a token's vision, it's set correctly and ready to go.