Pathfinder 1e Community sheet: Add-to-Roll Macro bug

So I'm experiencing a bug in the Pathfinder 1e community sheet where whatever is placed inside the "add to attack" field is what is also applied to damage if both fields contain the same query condition. I.E. if a power attack is applied to a roll as a query as follows: Add to attack: -[[?{Power Attack?|No,0|Yes,2}]] Add to damage: [[?{Power Attack?|No,0|Yes,4}]], and you resolve the query as a Yes the roll would resolve with a -2 applied to the attack roll and a -2 on damage instead of the appropriate +4.

Queries that are the same will only be resolved once in a roll.&nbsp; They must be unique to have unique outcomes.&nbsp; This is how queries work on roll20, not really a sheet issue.&nbsp; If you only want one query for the attack do something like; [[?{Power Attack?|No,0|Yes,1}*2]] [[?{Power Attack?|No,0|Yes,1}*4]] Here's an example for power attack on the PF sheet guide <a href="https://wiki.roll20.net/Pathfinder_Community_Sheet#Power_Attack.2C_Deadly_Aim" rel="nofollow">https://wiki.roll20.net/Pathfinder_Community_Sheet#Power_Attack.2C_Deadly_Aim</a> BTW: there is also a "Common Buff" (see the Buff's section of the sheet) for power attack on the sheet if you would rather toggle a buff vs having a query.

That's....interesting. The only reason I'm posting is because, in my experience, it had worked "correctly" for several years; that is to say you could have the same queries in separate fields and while they would resolve simultaneously they could provide different outcomes numerically to their respective rolls/values.

Sorry DnDigital, I could be wrong... but it's been my experience that identical queries within the same macro/roll will only be resolved once for all identical query locations.&nbsp; Since the PF sheet rolls everything for the attack at once (attack roll, crit confirm, damage, crit damage, etc. as well as all add-to-roll queries and macros), identical queries will all get resolved once in the attack roll.

Could be a Mandela effect scenario for me, but in either case so long as it's not a bug then all's good.