PF2e Remastered Strike Actions Guide

Introduction

Strike is the basic attack action in Pathfinder 2e Remastered. It covers weapon attacks, unarmed attacks, many bomb attacks, and a large share of martial turn planning. New players often read Strike and think "I attack three times." Experienced players read Strike and ask "what does the next attack need to roll, and what could this action do instead?"

Use this with the combat guide, three-action economy guide, flanking and positioning guide, grapple and control actions guide, movement actions guide, reactions guide, weapon traits guide, runes guide, and conditions guide.

The Short Version

Your first Strike is premium. It should get the biggest setup.

Your second Strike is negotiable. It depends on your accuracy, weapon trait, target defense, and alternatives.

Your third Strike is suspicious. It needs a real reason.

That is the whole guide in one paragraph. PF2e combat is not anti-attacking; it is anti-autopilot.

Rating Key

This guide uses practical table ratings for Strike decisions.

Strike Decision Rankings

Multiple Attack Penalty

Multiple attack penalty is the rule that stops PF2e from becoming "I full attack" every turn. After your first attack, later attacks on the same turn take a penalty. Agile weapons reduce that penalty. The details matter, but the play lesson is simple: every additional attack has to justify itself.

The first Strike is where you want your best math:

• Target is off-guard.
• Enemy is frightened, sickened, restrained, grabbed, or otherwise easier to hit.
• Ally has used Aid, bless-style magic, courage-style composition, or similar support.
• You know the target has a weakness or lower AC than its other defenses.
• Your weapon rune and damage type line up with the fight.

The second Strike is where class features and weapon traits start deciding the turn.

The third Strike is where pride goes to lose actions.

Better Uses For The Third Action

PF2e gives you many productive alternatives to a low-odds Strike.

Hot take: the best third action in PF2e is often the one that makes someone else's first action better.

Weapon Trait Rankings For Strike Builds

Read the weapon traits guide before building a martial character. Traits are not flavor text. They decide what your turn looks like.

Class Strike Rankings

Strike Setup By Condition

Conditions are attack math in disguise.

Use the conditions in combat guide and rules conditions guide for the full tactical picture.

Damage Type And Resistance

Strike optimization is not just "highest damage die." Player Core, GM Core, Monster Core, and equipment books all point at the same table lesson: damage type matters.

If your weapon damage is being resisted, switch tactics. Try a different weapon, bomb, spell, rune, alchemical item, or ally setup. If the target has a weakness, even modest damage can become excellent.

This is where Recall Knowledge earns its keep. A party that knows the enemy's weaknesses can make Strikes efficient. A party that refuses to ask questions often discovers resistance the expensive way.

Runes And Strike Scaling

Strikes depend on gear progression. The runes guide matters because weapon potency affects attack accuracy and striking runes affect damage dice. This is why PF2e treasure guidance is not decorative. If martial characters fall behind on expected weapon upgrades, their Strike turns feel worse quickly.

GM Core's treasure assumptions and automatic bonus progression both matter here. If the table uses normal treasure, keep weapon runes current. If the table uses automatic bonus progression, understand what gear math is being replaced and what item choices still matter.

Ranged Strike Notes

Ranged Strikes are not just melee Strikes from farther away. Cover, range increments, reload, volley, ammunition, thrown weapons, and enemy movement all matter.

Archers and firearm users should read the ranged weapons guide, firearms guide, Gunslinger guide, and skirmish warfare guide. Ranged characters often win by picking the right sightline, not by standing still and hoping the map stays polite.

Strike Flow Examples

Fighter Boss Turn

1. Stride or Step into flank.
2. Strike with best weapon and current rune math.
3. Raise a Shield, prepare for reaction play, or Strike again if the target is already debuffed.

The Fighter's high proficiency makes the second Strike more attractive than it is for many classes, but that does not make defense irrelevant.

Rogue Precision Turn

1. Move into flank, Hide, or Feint.
2. Strike while the target is off-guard.
3. Step away, Demoralize, Create a Diversion, or prepare the next off-guard plan.

For Rogue, "I hit" is less important than "I hit while the target is eligible for precision payoff."

Monk Mobility Turn

1. Flurry of Blows.
2. Stride to a better square.
3. Raise a defense, Trip, Grapple, Step, or pressure another target.

Monk's gift is not just attacking twice. It is attacking twice without spending the whole turn on attacks.

Alchemist Bomb Turn

1. Identify target weakness or resistance if possible.
2. Strike with the right bomb or item.
3. Use movement, draw/prepare item economy, or support the party rather than forcing bad follow-up attacks.

The bomb is a tool, not a personality.

GM Core Adjudication

GMs should make Strikes meaningful by making the battlefield meaningful.

Good Strike encounters include:

• Different enemy AC and save profiles.
• Cover and movement lanes.
• Enemies that punish careless positioning.
• Objectives that compete with attacking.
• Resistances, weaknesses, and damage-type clues.
• Terrain that makes reach, range, and mobility matter.

Do not solve Strike spam by arbitrarily making attacks bad. Solve it by making other actions visibly useful. When Demoralize, Recall Knowledge, Trip, Step, Take Cover, and Raise a Shield matter, players naturally stop treating the third action like a vending machine for disappointment.

Common Mistakes

Mistake 1: Treating Three Strikes As A Default Turn

Three Strikes can be correct, but it should be chosen, not assumed. If the third attack needs a miracle, you probably had a better action.

Mistake 2: Ignoring Weapon Traits

A bigger damage die does not automatically mean a better weapon. Reach, agile, trip, grapple, finesse, and thrown traits often change more turns than a small die increase.

Mistake 3: Forgetting Defense

PF2e crits hurt. Raise a Shield, Step, and Take Cover are offensive actions in slow motion because they keep you standing long enough to take better turns later.

Mistake 4: Attacking Into Resistance

If the damage type is bad, adapt. Carry backups. Ask questions. Let casters and alchemists do the jobs they are built to do.

Mistake 5: Making Spellcasters Feel Guilty For Not Striking

Most casters do not need weapon Strikes to contribute. Their version of "attack math" often lives in save targeting, focus spells, buffs, debuffs, and battlefield control.

Best Follow-Up Guides

• Three-Action Economy: the broader turn-planning guide.
• Action Compression Feats: how to do more without wasting actions.
• Flanking And Positioning: how to make melee Strikes better.
• Grapple And Control Actions: when control beats damage.
• Movement Actions: why movement is not a tax.
• Reactions: how to threaten outside your own turn.
• Weapon Traits: the real weapon-building guide.
• Runes: the gear math behind martial accuracy and damage.
• Combat Spells: when magic should replace or set up attacks.

Final Hot Take

Strike is the most common action in PF2e, but it is not the whole combat system. The strongest martial players are not the ones who attack the most; they are the ones who know which attack deserves the turn.

Return to the PF2e combat guide.