The campaign's default token settings don't actually get used for new tokens

I am moving this topic from Specific Use Questions to Bug Reports since it has become clear from my original topic that this is in fact a bug and not just something that I'm doing wrong. Here is the original topic: <a href="https://app.roll20.net/forum/post/8582208/the-campaigns-default-token-settings-dont-actually-get-used-for-new-tokens/?pageforid=8582535" rel="nofollow">https://app.roll20.net/forum/post/8582208/the-campaigns-default-token-settings-dont-actually-get-used-for-new-tokens/?pageforid=8582535</a> At this point I have also cleared my cache, cookies, and site data for roll20.net, app.roll20.net, and roll20.zendesk.net, which didn't solve the problem. Below is my Firefox console log, in a Firefox session in which I: Opened the Roll20 website Went into the game settings page to ensure that the token default settings have the two checkboxes ticked like I want Saved the game settings again just to be absolutely sure, even though I didn't change anything Launched the game Created a new token by dragging an image from the art library onto the map Opened the token's properties and confirmed that the two checkboxes are turned off Gave the token a name, then closed the token's properties to confirm that the nameplate didn't appear Opened the token's properties again and manually ticked the two checkboxes Closed the token's properties to confirm that the nameplate did appear Went back into the token's properties again to untick the two checkboxes Closed the token's properties again and confirmed that the nameplate disappeared again

Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). editor :12:1 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). editor :13:1 This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. editor JQMIGRATE: Logging is active jquery.migrate.js :20:10 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). 3 jquery-1.9.1.js :1444:6 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). 3 jquery-1.9.1.js :1450:5 CAMPAIGN ID: 3918832 instrument.ts :129:35 RTCIceServer.url is deprecated! Use urls instead. 3 app.js :278 70 instrument.ts :129:35 Custom Sheet Translation instrument.ts :129:35 TOUCH SUPPORTED: false instrument.ts :129:35 USING WEBGL ACCELERATION... instrument.ts :129:35 WEBGL STARTUP SUCCESS instrument.ts :129:35 Loading Custom character sheet. instrument.ts :129:35 Including compendium template css. instrument.ts :129:35 tuts loaded instrument.ts :129:35 Invalid URI. Load of media resource failed. editor Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). inspectlet.js :4:8118 Starting up WEB WORKER sheetsandboxworker.js :682:10 Starting up WEB WORKER sheetsandboxworker.js :682:10 unreachable code after return statement ffmpeg-worker-webm.3.js :153:13433 unreachable code after return statement ffmpeg-worker-webm.3.js :164:111617 unreachable code after return statement ffmpeg-worker-webm.3.js :183:15520 unreachable code after return statement ffmpeg-worker-webm.3.js :187:17706 unreachable code after return statement ffmpeg-worker-webm.3.js :187:19502 unreachable code after return statement ffmpeg-worker-webm.3.js :189:21299 unreachable code after return statement ffmpeg-worker-webm.3.js :190:21237 unreachable code after return statement ffmpeg-worker-webm.3.js :194:17922 unreachable code after return statement ffmpeg-worker-webm.3.js :194:39367 unreachable code after return statement ffmpeg-worker-webm.3.js :197:71233 Final page load. instrument.ts :129:35 Auth'ed. instrument.ts :129:35 Go post auth! instrument.ts :129:35 initial setup instrument.ts :129:35 joining game... instrument.ts :129:35 Player -LSC-DQ1dip1GHdp0Wr- is offline... instrument.ts :129:35 THREE.WebGLRenderer 69 instrument.ts :129:35 Full load page! 14 instrument.ts :129:35 We have 65 pages instrument.ts :129:35 Player -LSCDG3VdV6KKEE0a6nM is offline... instrument.ts :129:35 Player -LSD6oo7wdkfZBtt0TML is offline... instrument.ts :129:35 Player -LSFgbZ1xh4vaQWg6GyR is offline... instrument.ts :129:35 Deferred finish joining... instrument.ts :129:35 Firebase Online instrument.ts :129:35 Successfully compiled asm.js code (total compilation time 1898ms) ffmpeg-worker-webm.3.js This site appears to use a scroll-linked positioning effect. This may not work well with asynchronous panning; see <a href="https://developer.mozilla.org/docs/Mozilla/Performance/ScrollLinkedEffects" rel="nofollow">https://developer.mozilla.org/docs/Mozilla/Performance/ScrollLinkedEffects</a> for further details and to join the discussion on related tools and features! editor MediaStreamError { name : "NotAllowedError" , message : "The request is not allowed by the user agent or the platform in the current context." , constraint : "" , stack : "" } instrument.ts :129:35 ReferenceError: token is not defined app.js :577:1249 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at <a href="https://sentry.roll20staging.net/api/10/store/?sentry_key=fe596f386bb14775b58cad9accd672d0&amp;sentry_version=7" rel="nofollow">https://sentry.roll20staging.net/api/10/store/?sentry_key=fe596f386bb14775b58cad9accd672d0&amp;sentry_version=7</a> . (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). JQMIGRATE: jQuery.fn.attr('checked') may use property instead of attribute instrument.ts :129:35 console.trace() jquery.migrate.js :41:13 &nbsp;&nbsp;&nbsp;&nbsp; jQuery 4 &nbsp;&nbsp;&nbsp;&nbsp; render app.js : 561 &nbsp;&nbsp;&nbsp;&nbsp; showDialog app.js : 561 &nbsp;&nbsp;&nbsp;&nbsp; initialize app.js : 559 &nbsp;&nbsp;&nbsp;&nbsp; trigger base.js : 7 &nbsp;&nbsp;&nbsp;&nbsp; do_showRadialMenu app.js : 570 &nbsp;&nbsp;&nbsp;&nbsp; jQuery 2 &nbsp;&nbsp;&nbsp;&nbsp; sentryWrapped helpers.ts : 85 ​

Hi LockeZ, Apologies for the trouble - we're aware of the issue and are currently working to address it. Future communications on this issue should be&nbsp; redirected here . Thank you!