Hi Damian, I had a quick look at the sheet in a test game and can confirm there is an issue with the Quick Menu rolls. To me, it looks like the roll that's sent to chat fails because of the unrendered "&quot;" Skills for example; here's the macro as seen in the html in the browser's inspector <button class="unstyled-button btn ui-draggable" type="roll" name="roll_Skills_macro" data-i18n="SKILLS" value="/w &quot;@{character_name}&quot; &amp;{template:swn-default} {{charname=@{character_name}}} {{title=^{SKILLS}}} {{buttons=@{macro_skills}}}">Skills</button> and here's what's sent to chat; /w &quot;@{Vesrin|character_name}&quot; &{template:swn-default} {{charname=@{Vesrin|character_name}}} {{title=^{SKILLS}}} {{buttons=@{Vesrin|macro_skills}}} if the "&quot;" is removed or replaced with a quote directly; /w "@{Vesrin|character_name}" &{template:swn-default} {{charname=@{Vesrin|character_name}}} {{title=^{SKILLS}}} {{buttons=@{Vesrin|macro_skills}}} The roll works as expected. Using &quot; around the character_name within sheet macros is used so that any character names that included quotes within the name would still render properly and not break a macro. My
guess is that roll20 may have changed how it parses &quot; when it's embedded within single quotes in the html. So code like value = ''/w &quot;@{Vesrin|character_name}&quot; ..." will work, but value = '/w &quot;@{Vesrin|character_name}&quot; ...' will fail. It looks like the SWN sheet does use a single quotes around these macros I "believe" the sheet would probably just need to change to using double quotes around those macros. Or maybe roll20's Devs could have a look? I would politely DM the sheet author(s), Karl H. , and Panzer Post back if you need more help with this. Cheers