Chat Menu broken

I’m trying to build a chat menu for skill checks, but it’s not going how I hoped. I have the following ability written into a character sheet: /w "@{character_name}" &{template:default} {{ [Balance](~balance) [Bluff](~bluff) [Search](~search) [Sneak](~sneak) [Steal](~steal) [Traverse](~traverse)}} And all the appropriate abilities are written as well.  When I test the individual abilities, they work as expected.  When I test the chat menu ability, the buttons appear in chat, but clicking them returns: “ TypeError: Cannot read properties of undefined (reading 'substring')” What obvious thing am I missing?

When you're testing your chat menu ability; are you in editing mode when you click the roll button or are you saving with the tick button then rolling? I ask because ability buttons don't work properly when you roll the ability whilst editing.

When the command buttons are in a chat menu, you still need to include the character reference. I think this might work (untested):  [Balance](~@{character_id}|balance) It might require the prefix trick to make it work.

Yep, including the character reference worked! What’s the prefix trick?

<a href="https://app.roll20.net/forum/post/5899495/roll20-tips-and-tricks-innovative-solutions-to-common-problems/?pageforid=6137639#post-6137639" rel="nofollow">https://app.roll20.net/forum/post/5899495/roll20-tips-and-tricks-innovative-solutions-to-common-problems/?pageforid=6137639#post-6137639</a>

Thanks!&nbsp; Wrapping my head around that. To put a cap on this, I kept poking around and realized the way I originally wrote it (as posted above) actually did work when I used it through a token button, just not through the test button on the sheet until I included the specific character reference.&nbsp; Which seemed weird, but also not really a problem?&nbsp; So I went back to that to be cleaner.&nbsp; And RainbowEncoder, I swear I closed editing mode and was testing with the button after saving the ability and it wasn’t working...but now doing that seems to work fine?&nbsp; So, points to you, I think that was the solution but either some bug was affecting me or it was operator error.