Tag Archives: delay

What to Do When a D&D Player Wants to Be Ready, Call a Shot, or Delay

9 Replies

Without knowing any rules—without knowing a d20 from a d12—new Dungeons & Dragons players can join a party and love the game at least as much as veteran players. Everything feels fresh and thrilling, so often the newcomers have more fun. They play without rules by just imagining themselves as heroes and asking what they would do.

For the rest of us, knowing the rules can interfere with that primal experience. Instead of interacting with the D&D world, we slip into interacting with the rules. So when we hear footsteps approaching a door, instead of nocking an arrow and drawing a bow, we ask to ready an attack action for when a monster opens the door. In this example, that ready action breaks the rules because ready only applies during combat’s initiative order.

My last post described 3 times when players ask to use rules not even in the game. The game omits the supposed rules because they would run against D&D’s design approach. Often, past editions of the game even included these extra rules, but fifth edition’s more economical design forced them out. That post explained the designers’ choices and how to explain the missing rules to players.

Still, although the rules only allow ready actions in combat, lack a system for called shots, and omit the delay action, characters can still aim a drawn bow at a closed door, shoot for the tentacle gripping a friend, and perhaps even wait for the slow paladin to stop blocking the door.

This post offers advice for ruling on all those requests without inventing rules that the designers skipped for good reasons.

1. Readying an action outside of combat.

Players usually ask to ready outside combat for one of two reasons:

  • They expect trouble and want to stay alert.

  • They want to attack first. 

D&D lead rules designer Jeremy Crawford explained how he handles the request to stay alert. “Usually what that means is they won’t be surprised at my table.” Alternately, you could grant the character advantage on perception checks and a cooresponding +5 to passive perception until the situation changes or you judge that the characters’ attention would ease to a normal level. Nobody can stay especially alert all the time except barbarians with Feral Instinct. Impinging on a class feature would make barbarians angry. You wouldn’t like that.

Often, attempts to gain the first attack fall under surprise rules. When a party prepares to attack something inside a closed door and that foe remains unaware of the threat, then the monster starts combat surprised. If the monster knows about the threat, then the situation matches the usual start of a fight: Everyone is ready. Roll initiative to see who goes first. DMs who rule that a character with an arrow pulled only needs an instant to aim and shoot might give that character advantage on initiative. Don’t make the first attack automatic. We’ve all seen countless scenes where some skilled fighter stares down a poised weapon, and then uses lightning reflexes to strike first.

2. Called shots.

Usually players ask to call shots to gain a quicker route to taking a foe from a fight. To that I say, “Your characters are experts at combat. With each attack, they use their skills to find the best opportunity to land a blow that deals the most damage and that offers the best chance of taking your foe out of the fight.”

The second-edition Dungeon Master’s Guide limited called shots with a rule that remains sound in fifth. “Against a creature, a called shot will only cause the normal amount of damage allowed by the weapon. Attempts to blind, cripple, or maim will not succeed.”

Such a limit quashes most interest in called shots, so the designers opted for rules economy over adding rules for called shots. Still, players may want to temporarily impose a condition like Blinded, Deafened, or Prone. Conditions in D&D typically last a round or allow saves every turn. Players could also aim to distract, slow movement, or disarm.

The latest Dungeon Master’s Guide includes rules for disarming a foe (p.257). For other conditions, game designer Justin Alexander suggests some sensible, but untested rules. His post details the design decisions behind called shots. Called shots typically suffer a penalty of -2 or -4 as judged by the DM. (Don’t impose disadvantage, because that creates an incentive to call a shot whenever an attack would suffer disadvantage anyway. D&D lacks double disadvantage.) If the called shot succeeds, then you deal damage normally and the target must make an appropriate saving throw or suffer the effect. I recommend calculating a saving throw DC using a formula similar to the Battle Master fighter’s Maneuver save DC. Add 5 + your proficiency bonus + your choice of Strength or Dexterity modifier. 

Delay a turn.

Fifth edition skips the delay action because the extra option adds extra rules baggage and may slow play.

Nonetheless, in one case players who delay their place in initiative can smooth play without adding any complexity to the rules. That case comes when you first arrange initiative before any creature takes an action. Too often, the slow, tough characters at the door roll low while the quicker skirmishers in back roll high. Those tanks wind up bottling up the door because the rules offer no way for the bladesinger in back to just wait for the paladin to step out of the damn way. Before initiative starts, let players opt for a lower initiative count.

For the players who enjoy the tactical intricacies brought by the delay action, groups can import the delay rules in earlier editions of D&D and in D&D’s sister system Pathfinder. Here are the rules the designers wished to avoid.

Delay

By choosing to delay, you take no action and then act normally on whatever initiative count you decide to act. When you delay, you voluntarily reduce your own initiative result for the rest of the combat. When your new, lower initiative count comes up later in the same round, you can act normally. You can specify this new initiative result or just wait until sometime later in the round and act then, thus fixing your new initiative count at that point.

You never get back the time you spend waiting to see what’s going to happen. You also can’t interrupt anyone else’s action (as you can with a readied action).

Your initiative result becomes the count on which you took the delayed action. If you come to your next action and have not yet performed an action, you don’t get to take a delayed action (though you can delay again).

If you take a delayed action in the next round, before your regular turn comes up, your initiative count rises to that new point in the order of battle, and you do not get your regular action that round.

When you Delay, any persistent damage or other negative effects that normally occur at the start or end of your turn occur immediately when you use the Delay action. Any beneficial effects that would end at any point during your turn also end. You can’t Delay to avoid negative consequences that would happen on your turn or to extend beneficial effects that would end on your turn.

3 Actions D&D Players Want That Defy the Game’s Design Choices

18 Replies

Sometimes Dungeons & Dragons players ask to do things that the rules don’t handle—and not just because no roleplaying game’s rules can cover everything. The game omits the added rules because they would run against D&D’s design approach. Often, past editions of the game even included these extra rules, but fifth edition’s more consistent design forced them out.

This post isn’t about the rules fifth-edition Dungeons & Dragons could have included, but which the design skips for brevity. The D&D designers intentionally avoid providing rules for everything. “We want a system that trusts the DM to make the right call for any particular situation, rather than create many highly specific chunks of rules text in an attempt to cover every possible situation,” writes designer Rodney Thompson.

What actions aren’t covered by the D&D rules because they defy the game’s design choices?

1. Readying an action outside of combat.

In the early days of D&D, players liked saying, “I ready my sword” or “I nock an arrow.” Back then, initiative ran by house rules and DM whim, so this sort of declaration might win an edge. In an example of playing D&D that Gary Gygax wrote for the Europa zine in 1976, the DM grants the party +1 to a d6 initiative roll for being prepared. Only Unearthed Arcana (1985) actually put a benefit for readiness into print. “A bow specialist who begins the round with arrow nocked, shaft drawn, and target in sight is entitled to loose that arrow prior to any initiative check.” (See For 10 Years D&D Suffered From an Unplayable Initiative System. Blame the Game’s Wargaming Roots.)

Despite the lack of rules benefits, such declarations might prevent an adversarial dungeon master from deciding that because you never said that your sword was drawn, a fight caught you unprepared. In those days, many gamers saw thwarting and punishing players as part of the DM’s role. That attitude has fallen from favor. Nowadays, even though you never mention that your character started the day by putting on pants, we still assume pants.

The old spirit of readiness continues today. In a Sage Advice segment, D&D lead rules designer Jeremy Crawford says, “People often want to ready actions before combat has even started.”

Why “readying” does nothing. Jeremy says, “The ready action is an action you take in combat, so there’s really no such thing as readying before combat has started.”

What a DM should say. Maybe nothing. “I rarely correct them,” Jeremy says. He interprets the ready request as the player signaling their intent to stay alert. “Usually what that means is they won’t be surprised at my table. So even though I won’t have the mechanics of the ready action play out, I will still reward them for thinking in advance and signaling intent.”

To more rules-oriented players say, “In D&D, everyone who isn’t surprised starts a fight ready. Initiative lets us decide who among the ready combatants goes first.” (Surprised combatants also have a place in initiative, but they take no actions while surprised.) For more on what to tell players about initiative, see What to do when a player interrupts a role-playing scene to start a battle.

2. Called shots.

Sometime in every player’s D&D career, they get the idea of skipping the process of hacking through all a creature’s hit points by simply chopping off their weapon hand or blinding them with a blow to the eyes. Earlier editions of D&D termed attacks that aimed for a specific body part “called shots” and the game once included rules for such strikes. No more.

Why the rules don’t include called shots. The fifth-edition Player’s Handbook explains, “Hit points represent a combination of physical and mental durability, the will to live, and luck.” That’s a lot of possibilities. The game rules rely on this vagueness to allow characters to regain all their hit points after a short rest rather than a long hospital stay.

The moment characters start attempting to gouge their foes’ eyes out and villains return the favor, the game loses the useful abstraction of hit points. Also, if aiming for a particular body part proved more effective, why would anyone bother with regular attacks? The second-edition Dungeon Master’s Guide allowed called shots, but explained, “Because the AD&D game uses a generalized system for damage, called shots cannot be used to accomplish certain things. Against a creature, a called shot will only cause the normal amount of damage allowed the weapon. Attempts to blind, cripple, or maim will not succeed.”

What a DM should say. “Your characters are experts at combat. With each attack, they use their skills to find the best opportunity to land a blow that deals the most damage and that offers the best chance of taking your foe out of the fight.”

3. Delaying an action.

In third and fourth edition, players could delay their actions to later in the initiative count. This helped players coordinate actions with other players using an advanced strategy called you set ’em up and I’ll knock ’em down. Players who remember the flexibility of delaying still ask for it.

Why the rules don’t include delaying. The fifth-edition designers chose to eliminate delaying to simplify the rules and speed play.

Many spell durations and combat effects last until the beginnings and endings of turns. An option to delay complicates the rules for such effects and the bookkeeping needed to track them. “Simply by changing when your turn happens, you could change the length of certain spells,” explains the Sage Advice Compendium. “The way to guard against such abuse would be to create a set of additional rules that would limit your ability to change durations. The net effect? More complexity would be added to the game, and with more complexity, there is greater potential for slower play.”

An option to delay encourages players to analyze and discuss the optimal order for their turns during every round. “Multiply that extra analysis by the number of characters and monsters in a combat, and you have the potential for many slow-downs in play.”

What a DM should say. “Everyone in a fight acts at once. We just have turns to make some sense of that activity. If you delay, you do nothing while everyone else acts. At best, you can start an action and attempt to time it so that it finishes right after something else happens. That’s called readying an action.”

Revisiting three corners of the new D&D rules

3 Replies

In two posts, I answered some common rules questions about fifth-edition Dungeons & Dragons from dungeon masters and players. I added some extra comments on the answers because that’s what I do here.

Reaching 0 hit points, as shown in my DM screen

Rules for reaching 0 hit points, as shown on my DM screen

Since posting my answers, more game play has sparked some new observations.

What spells can I cast? As I introduced players to the game, the what-spells-can-I-cast question was asked a lot. I struggled to find a concise explanation until I arrived at this metaphor: The spells you prepare become the menu of spells that you can order from through the day. Your spell slots tell how many items you can order from the menu. If you really like Magic Missile, and you have it on your menu of prepared spells, order as many as you like until you reach your limit of slots.

How do opportunity attacks work? You only provoke opportunity attacks when you move out of an enemy’s melee reach. This change seems minor, but it alters tactics.  Your front line becomes less sticky than in earlier editions. Concentrating attacks becomes easier as characters in a party’s middle ranks grow more vulnerable. An attacker can circle your tank and potentially attack the wizard in the next row without provoking any opportunity attacks.

Can I delay? No. Back in my year-old post of D&D next questions and answers, I commented on the lack of a delay action in the rules. I even asked Mike Mearls about the absence and he thought the lack might even be an oversight—the product of playtest rules in flux. I predicted that the delay action would return to the final rules. I was wrong; delay is gone. For a while, I puzzled over the omission, but then a player at my table got paralyzed by a Hold Person spell, and the designers’ motives became obvious.

Delay may seem trivial, but the ability to delay forces the game to add rules for how delay interacts with effects that end during a player’s turn. On several occasions, I’ve seen fourth-edition players try to salvage their turn by asking if they can delay until, say, a stunned condition lifts. Fourth prohibited such shenanigans by including rules for how delay interacts with conditions that continue to end of turn.

Fifth edition potentially added another layer of complexity by adding concentration. For example, Hold Person requires concentration. This means that someone held can potentially delay, saving their turn and hoping that their allies can break the caster’s concentration. By removing delay, 5E prevents such tricks and eliminates some complicated rules.