Roll queries order

A quick and dirty question: is there any way to control the order of the popups generated by roll queries? Example of my current macro: &{template:default} {{name=Test}} {{Attack:=[[1d20cs>@{Critical}+@{BAB}+@{Dex|max}+@{Size}+@{Weapon}+@{Weapon|max}+@{Luck}+?{Studied target|0}*@{Studied}+?{Active masochism|0}*@{Masochism}+?{Smite evil|0}*@{Cha|max}+?{Active banes|0}*2+?{Attack modifier|0}]] against AC for [[@{Dice}d@{Dice|max}+@{Dex|max}+@{Weapon}+@{Luck}+?{Studied target|0}*@{Studied}+?{Active masochism|0}*@{Masochism|max}+?{Smite evil|0}*4+?{Damage modifier|0}+(?{Active banes|0}*2)d6+(?{Sneak attack|0}*@{SA})d@{SA|max}]] Slashing damage}} As you can notice this macro asks for: ?{Studied target|0} ?{Active masochism|0} ?{Smite evil|0} ?{Active banes|0} ?{Attack modifier|0} ?{Damage modifier|0} and ?{Sneak attack|0}, in the order they are called in the macro. Now is there any way to change that order (for example by calling each query before the main body of the macro, but without showing anything about this procedure in the chat log)?

You can use what is normally called the API hack for that. API commands are not shown in the chat, so prefacing with a line with an exclamation mark ! will cause them to be evaluated, but not displayed. Using the same query on later lines will use the earlier filled in value. ( NOTE: you do not need access to the API to use this trick. ): ! ?{Sneak attack|0} ?{Attack modifier|0} ?{Damage modifier|0} ?{Studied target|0} ?{Active masochism|0} ?{Smite evil|0} ?{Active banes|0} &{template:default} {{name=Test}} {{Attack:=[[1d20cs>@{Critical}+@{BAB}+@{Dex|max}+@{Size}+@{Weapon}+@{Weapon|max}+@{Luck}+?{Studied target|0}*@{Studied}+?{Active masochism|0}*@{Masochism}+?{Smite evil|0}*@{Cha|max}+?{Active banes|0}*2+?{Attack modifier|0}]] against AC for [[@{Dice}d@{Dice|max}+@{Dex|max}+@{Weapon}+@{Luck}+?{Studied target|0}*@{Studied}+?{Active masochism|0}*@{Masochism|max}+?{Smite evil|0}*4+?{Damage modifier|0}+(?{Active banes|0}*2)d6+(?{Sneak attack|0}*@{SA})d@{SA|max}]] Slashing damage}}

Thank you very much, that is EXACTLY what i was looking for, and i didn't know the trick was avaiable without API access.

no problem!