Queries used throughout Macro?

Hi so I am playing a pathfinder game and found very helpful posts about using macro queries to add modifiers to damage rolls based on many shot and rapid shot feats as well as Deadly aim, My question is this. Is there a way to ask a query that both affects the attack damage portion of the attack simultaneously so I don't have to have separate queries for say rapid shot in both the attack and damage section of the query? Basically I am wondering if its possible to have one queries submitted value be used in two separate places without making additional queries?

If it is the exact same value used in both places, yes.  If the value is different between the 2 places, then no.  The reason for this is that once you have answered a query in a macro, if that query comes up again in the macro, it will automatically be filled in with the value given the first time it was answered.  If it is the same value in both places, then you can plug in the query again in the damage section and you will only have to answer it in the attack for the value to be used both places when the macro calculates your results.

So I have to make sure the macro is identical for the ones that can be?

The question has to be identical.  You don't need to have the options listed for the second time around, but the question being identical is what is important.

Kraynic said: The question has to be identical.&nbsp; You don't need to have the options listed for the second time around, but the question being identical is what is important. Alexander, here's a link to another post where I've illustrated an example of what Kraynic means:&nbsp; <a href="https://app.roll20.net/forum/post/9174202/fun-macros-for-non-api-users-such-as-myself/?pageforid=9186299#post-9186299" rel="nofollow">https://app.roll20.net/forum/post/9174202/fun-macros-for-non-api-users-such-as-myself/?pageforid=9186299#post-9186299</a> .&nbsp; You can see that the second time the macro is called it doesn't list out all the options, or in the final example I show how that you can use a false API call (by putting an ! before the first query) to separate out the query from the macro itself.