I found an exploit where you could use the Roll Template Properties inside a url. This allowed a set of dice icons to be switched through the following options. d4-blank-280x280.png d6-blank-280x280.png d8-blank-280x280.png d10-blank-280x280.png d12-blank-280x280.png d4-blank-280x280-hitch.png d6-blank-280x280-hitch.png d8-blank-280x280-hitch.png d10-blank-280x280-hitch.png d12-blank-280x280-hitch.png Using the properties in the URL calling these images to change the dice value and to add -hitch if the result #rollWasFumble. < div class =" sheet-rolltemplate-result " style =" background-image: url(<a href="https://raw.githubusercontent.com/Roll20/roll20-character-sheets/master/CortexPrime-Hammerheads/assets/d{{physical_dice_size}}-blank-280x280{{#rollWasFumble()" rel="nofollow">https://raw.githubusercontent.com/Roll20/roll20-character-sheets/master/CortexPrime-Hammerheads/assets/d{{physical_dice_size}}-blank-280x280{{#rollWasFumble()</a> physical}}-hitch{{/rollWasFumble() physical}}.png); " > github link Something has changed since Monday - and now the {{properties}} in curly braces are being encoded before they are run, which means they are breaking the URL. When it worked it produced this kind of output - Now it produces this kind of output (font colour change was me trying something else) I'm considering alternative ways to do this. Possibly coding the different versions of the url call for each possible variation... this will cause a lot more code bloat. But I can see it as more stable. But I was really impressed with the discovery that embedding the logic in the URL call worked. Is this function going to be available again? Or was the exploit something that caused too many other issues and has had to be crushed? Just want to know how much work I need to redo.