[Pathfinder] Need help to make a macro that takes one attack roll and applies it to two weapons.

I'm playing a TWF Stalker in a pathfinder game and decided to take the 'Swift Claws' strike. Unfortunately this is proving to be frustrating to make a macro for. "Make an attack with two wielded weapons (or unarmed strikes), using the same attack action." The damages for the two weapons are seperate, and there's always a chance that at some point I could get two weapons with completely different enchantments (Or even worse, different crit ranges.) . I tried to accomplish this using the pathfinder sheet iterative attacks but I can't figure a way to make them both take the same intial attack roll. Can anyone help?

There is a Dual Wield option on the sheet.  To reveal the Dual Wield section on the Attacks tab, toggle from Settings|Sheet Configuration|Attacks|Use Dual Wield.  You can now take two of your created attack rowid's or the exact name of the attacks and create a new dual wielded attack.  You'll have to adjust mh/oh penalties manually according to raw.  Enjoy.

I know about the dual weild but that's not what this ability does. Both of the weapons get the exact same die roll applied to them. I kinda wanted it to work with crits.

Typhaaris said: Both of the weapons get the exact same die roll applied to them. Didn't notice that part. ;-( Curious, are you sure you do not roll the attack for each?&nbsp; ( <a href="http://paizo.com/threads/rzs2umcc?Define-Same-Attack-Action" rel="nofollow">http://paizo.com/threads/rzs2umcc?Define-Same-Attack-Action</a> ) Using the PF sheet, each attack(dual wield and iterative's included) is going to get it's own attack roll. I think an API script like powercards would be the only way to make one roll and apply it in multiple ways.&nbsp;

Hm.. Well, I know that the weapon attack macros look like this. Would there be some way to take out that initial '1d20' roll, roll it elsewhere and have THAT roll apply to both of them? Or is that not possible? {{attack=[[ 1d20cs&gt;[[ @{repeating_weapon_-l11gh4hsdzh4exffvre_crit-target} ]] + [[@{repeating_weapon_-l11gh4hsdzh4exffvre_attack_macro} ]] + @{attack-mod} ]]}} {{damage=[[@{repeating_weapon_-l11gh4hsdzh4exffvre_damage-dice-num}d@{repeating_weapon_-l11gh4hsdzh4exffvre_damage-die} + @{repeating_weapon_-l11gh4hsdzh4exffvre_damage_macro} ]]}} {{crit_confirm=[[ 1d20 + [[ @{repeating_weapon_-l11gh4hsdzh4exffvre_attack_macro} ]] + @{attack-mod} ]]}} {{crit_damage=[[ [[ @{repeating_weapon_-l11gh4hsdzh4exffvre_damage-dice-num} * (@{repeating_weapon_-l11gh4hsdzh4exffvre_crit-multiplier} - 1) ]]d@{repeating_weapon_-l11gh4hsdzh4exffvre_damage-die} + ((@{repeating_weapon_-l11gh4hsdzh4exffvre_damage_macro} ) * [[ @{repeating_weapon_-l11gh4hsdzh4exffvre_crit-multiplier} - 1 ]]) ]]}} {{precision_dmg1=@{repeating_weapon_-l11gh4hsdzh4exffvre_precision_dmg_macro}}} {{precision_dmg1_type=@{repeating_weapon_-l11gh4hsdzh4exffvre_precision_dmg_type}}} {{critical_dmg1=@{repeating_weapon_-l11gh4hsdzh4exffvre_critical_dmg_macro}}} {{critical_dmg1_type=@{repeating_weapon_-l11gh4hsdzh4exffvre_critical_dmg_type}}} {{weapon_notes=@{repeating_weapon_-l11gh4hsdzh4exffvre_notes}@{repeating_weapon_-l11ghsceg-3fsu2wtwl_notes}}} {{vs=@{repeating_weapon_-l11gh4hsdzh4exffvre_vs}}} {{vs@{repeating_weapon_-l11gh4hsdzh4exffvre_vs}=@{repeating_weapon_-l11gh4hsdzh4exffvre_vs}}} {{precision_dmg2=@{global_precision_dmg_macro}}} {{precision_dmg2_type=@{global_precision_dmg_type}}} {{critical_dmg2=@{global_critical_dmg_macro}}} {{critical_dmg2_type=@{global_critical_dmg_type}}} {{dual_precision_dmg=@{precision_dmg_macro}}} {{dual_precision_dmg_type=@{precision_dmg_type}}} @{iterative_attacks} @{macro_options} {{attack1name=@{iterative_attack1_name}}} {{attack2=[[ 1d20cs&gt;[[ @{repeating_weapon_-l11ghsceg-3fsu2wtwl_crit-target} ]] + [[ @{repeating_weapon_-l11ghsceg-3fsu2wtwl_attack_macro} ]] + @{iterative_attack2_value} ]]}} {{damage2=[[ @{repeating_weapon_-l11ghsceg-3fsu2wtwl_damage-dice-num}d@{repeating_weapon_-l11ghsceg-3fsu2wtwl_damage-die} + @{repeating_weapon_-l11ghsceg-3fsu2wtwl_damage_macro} ]]}} {{crit_confirm2=[[ 1d20 + [[ @{repeating_weapon_-l11ghsceg-3fsu2wtwl_attack_macro} ]] + @{iterative_attack2_value} + @{repeating_weapon_-l11ghsceg-3fsu2wtwl_crit_conf_mod} ]]}} {{crit_damage2=[[ [[ @{repeating_weapon_-l11ghsceg-3fsu2wtwl_damage-dice-num} * [[ @{repeating_weapon_-l11ghsceg-3fsu2wtwl_crit-multiplier} - 1 ]] ]]d@{repeating_weapon_-l11ghsceg-3fsu2wtwl_damage-die} + ((@{repeating_weapon_-l11ghsceg-3fsu2wtwl_damage_macro} ) * [[ @{repeating_weapon_-l11ghsceg-3fsu2wtwl_crit-multiplier} - 1 ]]) ]]}} {{precision_dmg21=@{repeating_weapon_-l11ghsceg-3fsu2wtwl_precision_dmg_macro}}} {{critical_dmg21=@{repeating_weapon_-l11ghsceg-3fsu2wtwl_critical_dmg_macro}}} {{precision_dmg22=@{global_precision_dmg_macro}}} {{critical_dmg22=@{global_critical_dmg_macro}}} {{attack2name=@{iterative_attack2_name}}} If that ruling is right then that will save me a whole lot of hastle. Though I don't think it is. There's another similar abiliity that specifically tells you that you make two whole attacks.

Typhaaris said: I'm playing a TWF Stalker in a pathfinder game and decided to take the 'Swift Claws' strike. Unfortunately this is proving to be frustrating to make a macro for. "Make an attack with two wielded weapons (or unarmed strikes), using the same attack action." The damages for the two weapons are seperate, and there's always a chance that at some point I could get two weapons with completely different enchantments (Or even worse, different crit ranges.) . I tried to accomplish this using the pathfinder sheet iterative attacks but I can't figure a way to make them both take the same intial attack roll. Can anyone help? Honestly, Make an attack with two wielded weapons (or unarmed strikes), using the same attack action, literally means you get 2 attacks per round. Separate rolls and separate damage. I am not a Pathfinder player but I would rule it that way if I was. So the Use Dual Wield feature of the PF character is your best option.

I'm not sure of the technical part, but once a macro is sent to chat, the rolls are handled by&nbsp; roll20/quantum .&nbsp; At that point, we can't do anything else to the roll.