A character gets stunned in the middle of their own turn. Do they lose the actions they haven’t spent yet, or finish the turn and pay later? The answer depends entirely on which game you’re running, and one of the two systems leaves part of the question genuinely open. Here’s how each handles it, where the real ambiguity lives, and the one-sentence house rule that prevents the argument.
The two systems at a glance
| D&D 5e | Pathfinder 2e | |
|---|---|---|
| What stunned does | Incapacitated (no actions or reactions), can’t move, speaks falteringly | You can’t act; usually carries a value (Stunned 1, 2, 3) that consumes future actions |
| Secondary effects | Auto-fail STR and DEX saves; attacks against you have advantage; concentration breaks (via incapacitated) | No reactions or free actions while stunned; overrides slowed |
| How it usually ends | Duration in the effect (e.g., until the end of the attacker’s next turn for Stunning Strike) | The value is paid off as you regain actions at the start of your turns |
| Mid-turn application | Immediate and total: your turn effectively ends | Partially contested; see below |
5e: the simple, brutal version
In 5e, stunned applies the moment it lands. The condition makes you incapacitated, and incapacitated means no actions, no bonus actions, no reactions, starting now, not at some future turn boundary. A monk’s Stunning Strike that connects mid-turn (say, off a readied attack or an enemy ally’s effect on your turn) shuts down everything you hadn’t done yet. The cascade is the part players underestimate: concentration breaks immediately because you’re incapacitated, melee attacks against you gain advantage, and you automatically fail Strength and Dexterity saves, which makes the follow-up shove, grapple, or Fireball land at full effect. A stunned 5e character isn’t just skipping a turn; they’re a vulnerability multiplier for as long as it lasts.
Pathfinder 2e: a value you pay off, plus one contested case
PF2e’s stunned usually comes with a number. The payment mechanic is clean: each time you regain actions at the start of your turn, reduce the actions you regain by your stunned value, then reduce the stunned value by the actions lost. Stunned 2 means your next turn starts with one action (and stunned drops to 0); Stunned 4 eats this turn’s three and one from the turn after. While the condition is on you, you also can’t use reactions or free actions, which is the quietly vicious part: a Stunned 1 champion isn’t just down an action, they’ve lost their reactive shield until it’s paid.
Two clean interaction rules ride along: stunned overrides slowed (you don’t stack the penalties; apply stunned), and actions you lose to stunned count toward actions you’d lose to slowed in the same window, so overlapping conditions don’t double-bill you.
The genuinely contested part
What happens to the actions you’re still holding when Stunned 1 lands mid-turn? The condition text says you can’t act while stunned, but the value mechanism only operates when you regain actions, which happens at the start of your turn, not in the middle of it. That tension supports two defensible readings:
| Reading | Mid-turn Stunned 1 means | Argument |
|---|---|---|
| Strict “can’t act” | Your remaining actions this turn are unusable, and you still regain one fewer action next turn | The condition text says you can’t act, full stop, while you have it |
| Regain-mechanism | You finish this turn normally; the value bites when you next regain actions | The value defines the cost, and the cost is explicitly charged at regain time; charging twice double-counts |
Neither reading is crazy, which is exactly why this needs to be a written table rule rather than a mid-combat debate. The strict reading makes stun effects (and the monsters that inflict them) meaningfully scarier; the regain reading is gentler and easier to track. Pick based on how lethal you want stun-capable enemies to feel, write the sentence down, and apply it both directions, to PCs and monsters alike.
My ruling
For 5e, I run it the simple way: stunned hits immediately, and anything you had left on your turn is gone. For PF2e, I’d use the stricter “can’t act” reading, mostly because it is easier to explain at the table and it makes the condition feel as dangerous as it should. I would not double-charge it casually, though — if that ruling is going to cost someone the rest of this turn and actions next turn, I want that written down before the fight starts, not invented in the moment. The big thing for me is consistency, because stun already feels bad enough without the ruling changing depending on who got hit.
Running stuns without wrecking the table
Stun is the strongest control effect in both systems precisely because it removes participation, and a player watching their character stand drooling for three rounds is not having fun, whatever the system. Practical guardrails: track it visibly (a die on the initiative tracker showing the remaining value or duration), announce the full consequences out loud when it lands (“you’re stunned, so your concentration on Haste ends and attacks against you have advantage”) so nothing feels like a gotcha, and ration how often enemies bring it. In PF2e specifically, stunned interacts with the dying rules in ugly ways for a party that can’t protect a downed ally, a dynamic we cover in our guide to character death in Pathfinder 2e. And in 5e, the action-economy math behind why losing one turn hurts so much is laid out in where 5e’s combat math breaks down.