Yeah, you can't do that, but you can include more in a query. A query is just asking you what tes=xt ou wnat to output, and that text is placed wherever the query is. This means that (in theroy, there is a porblem) you can do this: {{Skill Used=?{Skill| Deception,Deception}} {{Roll=[[1d20 + @{selected|Deception}]]| Agile Feint,Acrobatics}} {{Roll=[[1d20 + @{selected|Deception}]] } }} Everything after the comma and before the next | is output from the query. BUT Roll20 queries respond badly to certain characters. The characters , | and } are used by the query itself, so if you want to include them in the output, you have to replace them with temporary charcters (html Entities) that don't work the same, but that Roll20 will replace with the proper characters. These are called HTML Entities, because HTML represents them as the characters they replace, but Roll2 macros dont. So you could do this {{Skill Used=?{Skill| Deception,Deception}} {{Roll=[[1d20 + @{selected|Deception}]]| Agile Feint,Acrobatics}} {{Roll=[[1d20 + @{selected|Deception}]] } }} Notice that the } after Deception and Acrobatics have each been replaced twice, thats because } is a HTML entity that replaces }. A problem with HTML Entities (apart from them looking ugly), is that every time you open a macro containing them, the macro is processed and those HTML entities are replaced by the character they represent. So that } will become }, and the macro will break because you need those } for it to work. The most common solution to this is to place the "macro" in an Ability on a character sheet. Abilities do not do that parsing. This leads to creating a character sheet that is just for the GM, called maybe Macros, where all these macro-like abilities are stored. In conclusion, rolltemplates require html entities. HTML entities are a pain to deal with and often lead to the creation of Macros character sheets. But when using HTML Entities, you can reduce multiple query calls to just one. By the way, the devs did have a solution for teh qay queries work, had some glitches with it, and completely abandoned it. I feel they hsould have solved this solution by now, and just stopping macros from processing macro text the way abilities don't would go a long way.