So I'm prepping some roll macros for a Fate Accelerated game that I plan to run soon and I'm running into a problem. I'm not sure if what I want to do is possible with macros, but hopefully I'm just missing something obvious and one of you fine could point me in the right direction. I'm also not the most skilled code-boy out there, so apologies is a lot of this is explained poorly. I'm building a roll template and what I'm looking to have it do is: one one line display the name of the Approach (attribute) used, then next to it in parenthesis the value of said approach. On the next line roll the dice and add the value of that same Approach once again. Ideally I would like this to only query the use about what Approach to use once. Basically I need it to deliver the name of the attribute used once, and then the value of the attribute the next 2 times. My idea was to have the macro query the user for the name of the approach to be rolled. Then I can display the name, and reuse the same query again, but nested inside a call for the character's attribute, giving me both results while only bothering the user once. Here's what I have now: ?{Approach|careful|clever|flashy|forceful|quick|sneaky} &{template:default} {{name=@{selected|token_name}}} {{Action=ATTACK}} {{Approach=?{Approach} (+@{selected|?{Approach}})}} {{Roll=[[4df]]}} (Note: I haven't added the attribute query to the roll section yet, because I can't get it work earlier in the macro) And here's what it's delivering (after the error message: "No attribute was found for @{selected|?{Approach}"): As you can see, It worked correctly to deliver the name of the selected Approach, but not when I try to nest the query inside of @{selected) Is this simply not supported behavior with macros? Have I made a huge mistake? Am I just being dumb and screwed up something which should be simple? (Note that in Fate there are 4 basic actions, and each character has 6 "attributes". Right now I have 1 macro for each action, then then queries the user about what attribute to use. I could easily solve this by having a macro for each attribute and then querying for the action instead; But that would clutter the screen with extra token-actions and seems like it would be a slightly backwards thought process when going to roll)