Default vision setting doesn't seem to work (dnd5e)

I'm in the process of setting up a game and in my game settings I have vision disabled by default. However whenever I put down a new monster from my compendium it always seems to enable vision at first. I know I can disable it and then save the token settings, but is there a way to make it so by default?

When you say you " put down a new monster from my compendium", do you mean a monster from the compendium that was not already in your journal tab? The versions that are already in your game will not be overwritten by a compendium drop. If their vision is on, a compendium dropped token will always be that version. Test to make sure your campaign defaults are being honored by dragging in a monster you positively know is not already present in your game. It should follow your defaults.

Hi Keith I thought it was about campaign settings being changed and no in-game update being applied, so tested that and still got vision on for any never-before-used monsters dragged in from compendium.  Thought I must have missed something so set up a new game and set Dynamic Lighting on, token vision off.  Applied defaults. Opened game for first time, dragged a weird and thus never used monster on, still had token vision on?

Confirmed, the Compendium drag and drop is not respecting the Token Vision setting in the Campaign Details settings.  What is more, I cannot seem to find that setting in the Apply Default Settings checkboxes in the My Settings tab.  I've flipped the setting on in the CD's settings, then checked Apply Default Settings, not there.  Then I flipped the setting off in the CD's settings, then checked Apply Default Settings, still not there. 

I'll see if I can also confirm, but first, is this Jumpgate or Classic?

Classic for me, and I get random results. Recovered a game from cold storage and it went as expected, used a live but long-standing game, worked as well, but new game, not respecting settings.  Same monster, just to eliminate that from the equation

keithcurtis said: I'll see if I can also confirm, but first, is this Jumpgate or Classic? Classic Simon G. said: Classic for me, and I get random results. Recovered a game from cold storage and it went as expected, used a live but long-standing game, worked as well, but new game, not respecting settings.  Same monster, just to eliminate that from the equation I wonder if this might have something to do with a fix that was implemented awhile back regarding Compendium drag-drop not setting things correctly. 

I am getting odd results. Classic game, no changes,  Vision Campaign settings are off Creatures without darkvision coming in with vision off Creatures with Darkvision coming in with Vision and Darkvision on. Classic game, no changes,  Vision Campaign settings are toggled on, changes applied in-game Creatures without darkvision coming in with vision on Creatures with Darkvision coming in with Vision on and and Darkvision off.

So. I have an old sandpit where I have not used the Misc Apply Default Settings and I have a relatively new game where I have used that whilst messing with this.  Both games are set for DL restricts movement, DL Vision ON and Token Vision OFF Drop a Banderhobb (has darkvision 120ft) on the map, new creature to both games, definitely not in the journal of either game. Sandpit = No vision of any sort, as desired Couple of months old game, Apply Default definitely used  = Vision ON but night vision OFF, not as desired since Vision = ON Completely new game, DL restricts OFF, DL Vision OFF, Token Vision OFF, Banderhobb = Token Vision ON Night Vision ON Change DL Restricts to ON, Save defaults. Back in to game, exit and reload, Misc Apply Defaults, refresh for good measure, drop Banderhobb Banderhobb = Token Vision ON Night Vision OFF go back to game settings, turn Campaign DL Vision ON but not token vision, save, into game, exit, reload, apply defaults, refresh, Banderhobb remains with vision but not night sight One last run, game settings, token vision ON, save, into game, same sketch, no change to Banderhobb, which has been deleted from Journal each time before the refresh.  As noted by Gauss, there is no Token Vision setting in the Apply Default under the token section, so wasn't expecting anything to change with that last one really. Interesting that DL restricts movement was the trigger for turning off night sight I then dropped a commoner on the map and it had vision ON, which was correct.  Went back out to campaign settings, turned token vision off, saved changes, reloaded game, cleared Banderhobb and Commoner off map and out of journal refreshed, applied Default Settings, this time Vision showed up under Token Settings, so selected that with a little skip in my heart, refreshed, dropped both back on from Compendium and now both are showing with Token Vision OFF as desired from these settings.

I then loaded up an old game where it wasn't working in as much that creatures without darkvision  had no vision, so all OK, but darkvision creatures were being loaded with vision but not night sight.  DL Restricts=ON, Campaign DL Vision=ON, Vision =OFF turned Token Vision ON, saved, went into game applied defaults (selecting Vision on Token Settings), refreshed and dropped same tokens down, both had vision, removed them from map and journal, exited game Into game settings, turned Token Vision OFF, saved, back into game, apply defaults, refresh, drop tokens on - neither has vision, which is as desired.  A faff, but the desired outcome can be achieved.  Here's where I find Roll20 have been working on this whilst I've been messing about and it's fixed anyway ; ))

Here's what I have my game set to. I'm using the dnd5e 2014 character sheets, I do have beta features enabled, but not the new compendium (because last I checked you couldn't search by creature types with it), and I'm not using the jumpgate features. Edit: I just checked. You can search by creature type now. I'll test it out on jumpgate and see if that fixes the issue. Edit 2: Nope still getting the same issue with the jumpgate features.

Hi Azrik, I'm afraid I have not been able to resolve this apart from the work around mentioned above.  Getting our table together is like herding cats and as such, they have given a hard NO to Jumpgate and 2024 until all the bugs are squished.  As such, am completely unable to advise wrt jumpgate