Oosh said: When you use those Command Buttons, [Button](~Command), the command part is looking for an Ability stored on a sheet. You can get some limited chat functionality by using (!
 .... ) in the parentheses, so you could do this: [@{selected|repeating_npctrait_$0_name}](!
@{selected|repeating_npctrait_$0_description}) Which would send the description straight to chat. You'd want to save this on a Macro Character, as the HTML substitution won't persist in a Collections macro. I don't think there's any way of getting a template to work by trying to ram the code inside a button. The other option would be to have a bunch of macros set up on a sheet which turn the trait into something nicer. For example, the first one would be: &{template:npcaction}{{rname=@{selected|repeating_npctrait_$0_name}}}{{description=@{selected|repeating_npctrait_$0_description}}} Save this as the Ability NPCtrait0 on a sheet called Macros. Then your button on your original macro becomes: [@{selected|repeating_npctrait_$0_name}](~Macros|NPCtrait0) It does involve creating a bunch of extra macros, depends on what you want it to look like, really. The first suggestion did not work. I am seeing descriptions stored in the sheet with (comments) in brackets or parentheses breaks the macro. That's no fault of the macro, that's on whoever wrote the description. The second macro you suggested ( in bold) Works fine on the npcaction template but not the npcatk template (which I prefer visually) but again that's not on the macro that's an error in the template. The second half of that suggestion failed though (for me anyways) but I am working with the second macro alone and that works for me. Thanks...