As a curiosity, I tried nesting the query function within an attribute. Specifically I wrote something like "@{CHARACTER|weapon-?{weapon}-name}" expecting that entering a number would put that number into the attribute it was nested in such as "@{CHARACTER|weapon-#-name} which would then finally return the name of the weapon I entered the number of. Instead, it seemed to parse the text differently than expected. I was properly asked for a value to which I entered "1", and I first got an error "No attribute was found for @{CHARACTER|weapon-?{weapon}" and then the text "CHARACTER|weapon-1" as usually happens when I enter an unrecognized attribute. When I tried using a default value such as in "@{CHARACTER|weapon-?{weapon|1}-name}", the value in the query prompt was instead had "1-name" (no curly brace) initially to which entering resulted in "No attribute was found for @{CHARACTER|weapon-?{weapon}" and "CHARACTER|weapon-1-name". It seems that the attribute function itself was only scanning until the first closed-curly-brace ignoring anything in between regardless as if there were any other macros or functions nested in. But whatever macros are there are still executed independently. I'm not surprised actions like this weren't anticipated, but it could add a bit of flexibility if you can get it to work properly. If you somehow get it to properly parse out and follow order of operations, this could potentially work.
