D&D 5e Combat Rules & Conditions Questions for Dungeon Masters

Under the 2024 rules, tremorsense does not remove the effects of the Blinded condition. Blinded says that attack rolls against the creature have Advantage and the creature’s own attack rolls have Disadvantage. Tremorsense can locate moving creatures and objects within its range when they share the same surface or liquid, but it explicitly is not a form of vision.

That means the insect can know where a moving, grounded target is without being able to see it. It still suffers the Blinded attack modifiers unless another trait specifically says otherwise. Tremorsense also does not detect creatures or objects in the air, so destroying the eyes can still create additional tactical openings.

If this is a homebrew monster and the intended design is that destroying the eyes weakens it without making it poor at attacking anything it can feel, write that exception into the weak-spot trait. For example, the trait could say that while blinded by the destroyed eyes, the monster ignores Blinded’s attack-roll effects against targets it detects with tremorsense.

That would be a house rule built into the monster. Rules as written, tremorsense provides location information; it does not cancel Blinded.

In D&D 5e, a critical hit is normally triggered by an attack roll that scores a natural 20. The attack hits, and its damage dice are rolled twice; fixed modifiers are added once. Damage dice that are part of the attack are generally included in the critical hit, while flat bonuses are not doubled.

For example, if an attack normally deals one weapon die plus a fixed ability modifier, the critical hit rolls two weapon dice and adds the modifier once. If the hit also includes additional rolled damage from a feature or effect, that additional damage may also be part of the critical damage calculation, depending on the feature’s wording. A saving throw does not become a critical hit merely because someone rolls a natural 1 unless a specific rule says otherwise.

Features can change the range or circumstances under which a critical hit occurs, so the general rule should be applied first and then modified by the specific feature involved. When resolving an unusual interaction, identify which dice are damage from the attack itself and which effects happen separately after the hit; that distinction usually determines what is doubled.

In D&D 5e, an attack hits when its attack roll equals or exceeds the target's Armor Class (AC), unless a specific rule changes the result. Roll a d20 and add the attack's relevant ability modifier and any applicable proficiency or other attack bonuses. Compare that final total with the target's AC, including any applicable adjustments.

For example, an attacker with a +5 attack bonus rolls 12 on the d20 for a total of 17. The attack hits AC 17 but misses AC 18. A natural 20 on the d20 hits regardless of the total and normally produces a critical hit; a natural 1 misses regardless of the modifiers. Advantage and Disadvantage affect which d20 result is used for the roll.

Do not confuse the attack roll with the damage roll. After an attack hits, roll its damage using the weapon, spell, or feature that generated it. Some spells or effects instead require the target to make a saving throw and do not use an attack roll at all.

When cover, reactions, magical defenses, or conditional bonuses apply, resolve them according to their timing. State the relevant AC and modifiers consistently rather than deciding success from the narrative description alone.

Rules reference: D&D 5e SRD 5.2.1 — Attack Rolls.

In 2024 5e, invisibility is a condition; it does not automatically mean that enemies lose track of where you are. While Invisible, you have advantage on Initiative if the condition is active when Initiative is rolled, effects that require seeing you cannot target you unless the creature can somehow see you, attacks against you have disadvantage, and your own attacks have advantage against creatures that cannot see you.

Those benefits are separate from hiding. The Hide action has its own requirements and check. If you successfully hide, the rules use the Invisible condition to represent being concealed, but becoming Invisible from a spell does not by itself say that your location becomes unknown. Creatures can still respond to noise, tracks, movement, or other information the situation provides.

The 2nd-level Invisibility spell also has a specific ending condition: it ends immediately after the target makes an attack roll, deals damage, or casts a spell. Greater Invisibility does not have those same early-ending triggers and can persist while the target fights, subject to concentration.

At the table, resolve three questions separately: can the creature be seen, has it successfully hidden, and does an effect require sight? That avoids most invisibility confusion.

In D&D 5e, a critical hit increases the damage dice rolled for a qualifying attack without doubling fixed damage modifiers. When an attack scores a critical hit, roll the attack's applicable damage dice twice and add the relevant modifiers once. This is different from doubling the final damage total.

For example, an attack that normally deals 1d8 plus 3 damage instead rolls 2d8 plus 3 on a critical hit. The fixed modifier remains unchanged. If an attack includes additional damage dice that qualify under the applicable rules, those dice may also contribute to the increased critical-hit damage. The exact interaction can depend on the feature, spell, and edition being used.

Critical hits are associated with attack rolls, not with every natural 20 rolled during play. A natural 20 on an ability check or saving throw does not automatically create critical-hit damage. Likewise, a spell that requires only a saving throw should not be treated as scoring a critical hit simply because a creature rolls a particular number.

For any unusually worded ability, identify whether its damage belongs to the qualifying attack and check the applicable 2014 or 2024 rule text before calculating the result.

In current D&D 5e, Initiative is a Dexterity check made when combat starts. Each participant rolls to determine turn order, and the combatants act from the highest Initiative total to the lowest. Because it is a Dexterity check, any rule that modifies the relevant check can affect Initiative when its wording applies.

The GM rolls once for a group of identical creatures, so all members of that group share the same place in the order. If two participants tie, the rules provide tie-breaking procedures rather than requiring a reroll of the entire combat.

SRD 5.2.1 also presents an optional Initiative Score rule. Instead of rolling, a creature can use 10 + its Dexterity modifier as its Initiative Score. Advantage adds 5 to that score and Disadvantage subtracts 5.

Do not mix the optional score method with the normal roll unless the table has deliberately adopted a hybrid house rule. For ordinary play, the calculation is simply the Dexterity check plus whatever specific features legitimately modify it.

Rules reference: D&D 5e SRD 5.2.1 — Initiative; Initiative Score.

If you are using the 2024 rules, Weapon Mastery is best treated as part of the classes that receive it, not as an optional bonus handed to every weapon user. A character only uses a weapon's mastery property when a feature gives that character access to mastery with that weapon.

That distinction matters for balance and identity. Mastery gives martial characters additional tactical decisions and makes weapon choice mean more than damage die size. Removing the feature from classes that are built around it reduces some of that differentiation; giving every proficient character unrestricted mastery does the opposite and expands a benefit beyond the features that grant it.

For a table worried about complexity, simplify presentation rather than deleting the system. Put each character's mastered weapons and their effects directly on the character sheet, introduce only the properties that character can currently use, and resolve the effect as part of the attack instead of reopening the rules every turn.

A house rule can certainly change Weapon Mastery, but make that an explicit table choice. First establish who receives mastery under the rules, then decide whether the extra tactical detail is helping your particular group.

D&D 5e uses thirteen damage types: acid, bludgeoning, cold, fire, force, lightning, necrotic, piercing, poison, psychic, radiant, slashing, and thunder. A damage type describes the nature of the harm and matters especially when a creature or feature has resistance, immunity, or vulnerability to that type.

Bludgeoning, piercing, and slashing commonly represent different physical attacks. Fire, cold, lightning, and acid identify familiar energy or substance hazards, while force, psychic, necrotic, radiant, poison, and thunder cover other forms of harm. The type is determined by the attack, spell, hazard, or other rule that causes damage; its narrative appearance alone does not automatically change it.

When resolving an effect, identify its listed damage type before applying a target's relevant defenses. Do not assume that two spells with similar descriptions deal the same type, or that a resistant creature is automatically unaffected by every additional condition attached to an attack. Separate the damage calculation from any other effect.

For homebrew creatures or spells, choose damage types deliberately. Overusing unusual resistances can change which characters are effective in encounters. State the type clearly in every custom effect so players can make informed choices.

In current 2024 D&D 5e, the Grappled condition does more than stop movement. A Grappled creature has Speed 0, has Disadvantage on attack rolls against targets other than the grappler, and can be dragged or carried by the grappler, with extra movement cost unless the target is sufficiently smaller.

A grapple is therefore mainly a positioning and control tool. It can stop an enemy from reaching another target, hold someone inside a hazardous area, move a creature away from an ally, or force the grappled creature to spend effort escaping. It does not automatically impose the Restrained condition, prevent spellcasting, make attacks against the target gain Advantage, or stop the target from attacking the grappler.

For a typical Unarmed Strike grapple, the target makes a Strength or Dexterity saving throw against the grappler’s escape DC. A Grappled creature can later use its action to attempt an escape with Strength (Athletics) or Dexterity (Acrobatics). The condition can also end if the grappler becomes Incapacitated or the target is moved beyond the grapple’s range.

Rules reference: D&D 5e SRD 5.2.1 — Grappled condition, Grappling, and Unarmed Strike.

D&D 5e does not give a special procedure for creatures that join an already-running combat, so the DM needs a consistent table procedure rather than rerolling the entire initiative order. I would roll initiative for the newcomers when they appear, finish the current creature's turn, and let the newcomers take their first turns on their initiative counts starting in the next round.

That removes the strange incentive for a newcomer to roll low enough to act immediately. It also avoids reshuffling everyone who is already fighting, which can produce consecutive turns, lost turns, and much more disruption than the new creatures justify. Once the creatures are actually present, I would allow them to make reactions normally if an appropriate trigger occurs; that is part of the table procedure, not a special RAW rule for reinforcements.

For reinforcements whose arrival is under the DM's control, an even cleaner option is to bring them onto the battlefield at the start of a round and roll their initiative then.

If a character opens a door halfway through their turn and discovers another group, let that character finish the turn. They created the new situation by spending movement or interacting with the environment; interrupting and rebuilding initiative is unnecessary. The tactical advantage is also accompanied by a real risk: opening another area can merge encounters and expose the party to more enemies. Consistency matters more here than finding a mathematically perfect insertion point.

A 2024 Rogue cannot apply Sneak Attack merely because a spell makes an attack roll. Sneak Attack requires a hit with an attack roll that uses a Finesse or Ranged weapon, along with the feature's other conditions. A normal spell attack that does not use such a weapon therefore does not qualify.

The important distinction is between a spell attack and a spell that tells you to make an attack with a weapon. True Strike is the clearest SRD example: as part of casting it, you make one attack with the weapon used as the spell's material component, and the spell allows the attack to use your spellcasting ability. If that weapon has the Finesse property or is a Ranged weapon, and you satisfy the normal Sneak Attack requirement for Advantage or an eligible nearby ally, the attack can qualify for Sneak Attack.

Do not generalize that result to every damaging cantrip. Read the spell's action precisely: does it create its own spell attack, force a saving throw, or instruct you to make a weapon attack? Sneak Attack cares about the qualifying weapon attack, not simply whether magic was involved.

Rules reference: D&D 5e SRD 5.2.1 — Rogue: Sneak Attack; True Strike.

A hidden creature does not normally get to “ready an attack before combat” and then resolve that attack outside initiative. The Ready action is taken on a creature’s turn, so once hostile action is about to begin, establish Initiative first. In the current rules, an ambusher who catches enemies unaware can impose Disadvantage on their Initiative rolls through Surprise, but everyone still enters the same Initiative order.

After Initiative is set, the hidden creature acts when its turn arrives. If it remains unseen, the normal benefits of being unseen or hidden can matter to the attack, but hiding does not create an extra pre-combat turn. On its turn, the creature can attack immediately or take the Ready action and specify a perceivable trigger for a later Reaction.

This distinction prevents ambushes from becoming automatic free rounds while still rewarding preparation. Position, stealth, Surprise, and the target’s ability to detect the attacker determine the advantage of the ambush; they do not bypass Initiative.

If the fiction begins with an attack already being attempted, that declaration is the signal to roll Initiative and resolve whether the attacker acts before the targets.

Rules reference: D&D 5e SRD 5.2.1 — Initiative, Surprise, Hide, and Ready.

No. Under the current D&D 5e rules, picking up a monster's weapon does not automatically give a player character the damage expression printed in that monster's attack. SRD 5.2.1 separates a monster's stat-block effects from equipment that other creatures can actually recover and use. If an item can be retrieved, it appears in the monster's Gear entry. When somebody else uses that item, it follows the normal rules for that piece of equipment, while monster-specific flourishes attached to its stat block are ignored. Equipment mentioned outside the Gear entry is treated as supernatural or highly specialized and is unusable once the monster is defeated. The GM can also give a monster additional equipment and decides whether that equipment remains recoverable and usable afterward. In practice, this means a monster attacking for unusually high damage does not leave the complete attack behind on the floor. That damage can represent the creature's strength, anatomy, training, special abilities, or stat-block design as well as the physical object. If a slain enemy carried an ordinary greataxe listed as recoverable gear, a character can use that greataxe according to the normal weapon rules; they do not copy the monster's attack damage. If you want an exceptional enemy weapon to become exceptional treasure, make that property explicit as part of the item and balance it as loot rather than transferring the monster attack wholesale.

A spellcaster can outdamage a martial archer in some rounds and some encounter types, but not as a universal rule. The answer changes with level, build, number of targets, available spell slots, rest frequency, magic items, and whether the comparison measures one explosive turn or sustained damage across several fights.

Compare like with like. Test at least three situations: burst damage against one priority target, sustained single-target damage over several rounds, and damage against multiple enemies. Then repeat the comparison across enough encounters that limited spell slots matter. A caster spending a high-level slot every round is solving a different resource problem from an archer whose main attacks remain available throughout the day.

Also count what each character gives up to produce damage. Concentration, positioning, setup rounds, ammunition, defensive options, and competing utility all matter. A spell that controls enemies may contribute more than its damage total suggests, while reliable ranged attacks can remain valuable when resources are depleted.

For table balance, watch actual spotlight patterns rather than theoretical peak numbers. If one character repeatedly makes another’s role irrelevant under the campaign’s real pacing, examine encounter variety, rest cadence, treasure, and build interactions before blaming one entire class category.

Rules reference: D&D 5e SRD 5.2.1 — Spellcasting: Spell Slots.

Yes. The Incapacitated condition by itself does not prevent a creature from making saving throws. If an effect says the target can repeat a saving throw at the end of its turn or at another specified time, becoming Incapacitated does not cancel that instruction unless the effect or another active rule says otherwise.

The confusion usually comes from reading “cannot take actions” as “cannot do anything.” A saving throw is not an Action, Bonus Action, or Reaction; it is a separate kind of d20 roll made when a rule calls for it. Incapacitated therefore does not create a blanket failure or prohibition.

Check the whole effect, however, because Incapacitated often appears together with other conditions. A different condition can impose additional restrictions or automatic failures on particular saving throws, and the spell or ability itself may specify when repeated saves occur or whether they stop under certain circumstances.

The practical method is simple: read the Incapacitated condition, then every other active condition, then the exact effect that created them. Apply all of those instructions together rather than inferring extra consequences from the everyday meaning of “incapacitated.”

Rules reference: D&D 5e SRD 5.2.1 — Incapacitated [Condition] and Saving Throws.

There is no universal D&D 5e rule that makes spellcasters consistently outdamage martial characters. The result depends on level, build, target count, encounter length, available spell slots, rests, magic items, and whether “damage” means one explosive round or sustained output across several fights.

Compare characters under the same scenario instead of using a single peak turn. Track at least three cases: burst damage against one important target, sustained single-target damage over several rounds, and damage against multiple enemies. Then repeat the comparison across enough encounters that limited resources matter. A caster who spends a high-level slot every round is answering a different question from one expected to preserve resources.

Also count opportunity cost. A spell that controls several enemies, protects allies, or changes the battlefield may be stronger than a damage spell even when its damage number is lower. Martial characters often contribute through reliable attacks without spending the same kind of daily resource.

For table balance, look for repeated spotlight problems rather than theoretical superiority. If one character regularly makes another’s combat role irrelevant under your actual pacing, adjust encounter variety, rest cadence, treasure, or character options before assuming the class category itself is the only cause.

Rules reference: D&D 5e SRD 5.2.1 — Spellcasting: spell slots.

No. D&D 5e has no general rule that a natural 20 automatically succeeds on every ability check or saving throw. For those d20 rolls, the normal procedure is to add the relevant modifier and compare the total with the target number; a specific rule can create an exception.

Attack rolls are different: rolling a 20 on the d20 has its own special attack rule and produces a Critical Hit. That familiar rule is often incorrectly generalized to every d20 roll.

For ability checks, the DM should also decide whether a roll is appropriate before dice are used. If a proposed action is impossible in the fiction, a natural 20 does not turn it into a possible action; there may simply be no check. If the action is possible but difficult, set or use the appropriate DC and resolve the check normally.

Saving throws follow the rule specified by the effect calling for the save. Some specific mechanics, such as Death Saving Throws, give particular meanings to certain die results, but those exceptions do not create a universal natural-20 rule for all saves.

Rules reference: D&D 5e SRD 5.2.1 — Ability Checks, Saving Throws, and Critical Hit.

No. The Grappled condition by itself does not prevent spellcasting or make a creature unable to use its hands. In SRD 5.2.1, Grappled sets Speed to 0, affects attacks against creatures other than the grappler, and allows the grappler to move the target; it does not add a spellcasting restriction.

Spell components still matter independently. A spell with a Somatic component requires at least one free hand for its gestures, and a Material component normally requires a free hand to access the material or focus. A normal grapple does not say those hands become unavailable.

If the fiction calls for pinning wrists, gagging a caster, or otherwise restraining the actions needed for components, make that a separate house-rule maneuver rather than silently expanding Grappled. Give it an explicit action cost, a save or other resolution method, and a clear way to escape. That lets stronger restraint exist without making every ordinary grapple an automatic anti-caster technique.

Rules reference: D&D 5e SRD 5.2.1 — Grappled condition and Spellcasting Components.

In D&D 5e, a character dies instantly if an instance of damage reduces them to 0 Hit Points and the remaining damage equals or exceeds their Hit Point maximum. Otherwise, the character normally falls unconscious and begins making death saving throws. Negative hit-point totals are not tracked.

For example, suppose a character has a maximum of 20 Hit Points and currently has 5. An attack dealing 24 damage reduces the character to 0, leaving 19 damage. Because 19 is less than the character's maximum of 20, the character does not die instantly.

If the same attack instead deals 25 damage, 20 damage remains after reaching zero. Because that remainder equals the character's maximum, the character dies immediately without making death saving throws.

This comparison uses the character's Hit Point maximum, not their Constitution score, character level, or number of remaining death saves.

Damage received when a character is already at 0 Hit Points follows a related but separate procedure: damage ordinarily causes a failed death saving throw, while damage equaling or exceeding the character's Hit Point maximum causes death.

The DM should calculate the damage remaining after reaching zero rather than treating a hypothetical negative total as a separate resource.

Rules reference: D&D 5e SRD 5.2.1 — Dropping to 0 Hit Points; Instant Death; Death Saving Throws.

D&D 5e does not need a universal called-shot rule for a player to describe attacking a specific body part. The safest default is to let the description remain fictional unless the existing attack or feature already creates a mechanical effect. A successful hit to an arm is still normal damage unless a rule or explicit ruling says otherwise.

If the player wants an extra effect—blinding an eye, disabling a hand, cutting a tendon—treat that as a trade rather than a free bonus. The DM can require a harder setup, reduced damage, a condition, a limited target, or an opposed check, depending on the situation. The important part is to define the consequence before the roll.

Avoid a standing rule that simply adds a small attack penalty in exchange for severe permanent effects. Players will use it constantly, and enemies logically could do the same, turning every fight into an attempt to remove limbs or senses.

Called shots work best as occasional adjudications for unusual situations: a visible rope, an exposed mechanism, a monster’s temporary weak point, or an enemy already close to defeat. Use existing conditions and object rules when possible, and reserve lasting injuries for moments where the fiction genuinely supports them.

Rules reference: D&D 5e SRD 5.2.1 — Attack action and Breaking Objects.

In current D&D 5e, a character can equip or unequip one weapon when making an attack as part of the Attack action, either before or after that attack. Equipping includes drawing or picking up a weapon; unequipping includes sheathing, stowing, or dropping one. This makes weapon switching more permissive than the older “one object interaction” shorthand many 2014 tables used.

Apply the rule attack by attack. A character with multiple attacks can potentially change what is in hand across those attacks, provided each equip or unequip is attached to an attack as the rule allows. That does not mean every inventory manipulation is free: shields, spell foci, ammunition, and nonweapon objects follow their own relevant rules.

The cleanest table practice is to ask players to state the sequence when it matters: “I draw the axe, make the first attack, stow it after that attack, then draw the sword with the second.” Most turns do not need that level of narration unless hand occupancy changes a legal option.

If the campaign uses the 2014 rules instead, use that edition’s object-interaction text rather than importing the current rule.

Rules reference: D&D 5e SRD 5.2.1 — Attack action; Equipping and Unequipping Weapons.

Use grouped initiative for identical monsters by default, then split important enemies into separate turns when doing so improves the encounter. The SRD specifically allows the GM to make one initiative roll for a group of identical creatures, which keeps ordinary fights moving quickly.

Grouping has a cost: several enemies acting consecutively can create large damage spikes before the players can respond. If that becomes a problem, divide a large group into two initiative groups rather than rolling separately for every creature. A boss, lieutenant, or monster with a distinctive role usually deserves its own initiative because its timing matters to the scene.

For very large encounters, prepare initiative groups before play: for example, archers, front-line creatures, and the commander. That is easy to track and gives the battlefield a readable rhythm. Avoid changing grouping mid-fight just to improve the monsters’ position; initiative procedure should feel stable rather than tactical on the GM’s side.

The SRD also gives monsters an initiative modifier and an initiative score, allowing the GM to use the score instead of rolling for a monster.

Rules reference: D&D 5e SRD 5.2.1 — Combat: Initiative and Monster Stat Blocks: Initiative.

Decide first whether the mount is controlled or independent, because that determines how its turn works. A controlled mount changes its initiative to match the rider’s and can move on that turn, but its action choices are limited to Dash, Disengage, and Dodge. An independent mount keeps its own initiative and acts according to its own judgment.

At the table, place rider and mount as one clear unit and track the mount’s movement separately from the rider’s actions. State whether a creature is trained and controllable before combat starts; uncertainty about that point causes more confusion than the movement rules themselves.

Mounted scenes improve when the terrain matters. Narrow doors, ladders, steep slopes, crowded streets, and creatures large enough to threaten the mount create decisions beyond “I move faster.” Also remember that a mount can be attacked, moved, or knocked down, so make its position visible rather than treating it as equipment.

Do not invent extra restrictions simply because mounted movement is powerful. Use the actual space, terrain, and enemy behavior to create pressure, then adjudicate unusual stunts consistently.

Rules reference: D&D 5e SRD 5.2.1 — Combat: Mounted Combat.

Nick moves the extra attack granted by the Light weapon property into the Attack action instead of requiring a Bonus Action. It does not grant a wholly separate additional attack. The 2024 rule allows this Nick-enabled extra attack only once per turn, and the character must have access to the relevant weapon mastery. Normally, attacking with a Light weapon using the Attack action permits an extra attack with a different Light weapon as a Bonus Action later that turn. If the extra attack uses a weapon whose Nick mastery you can employ, you can make it during the Attack action. For instance, attack with a shortsword, then make the eligible extra attack using a dagger with Nick; your Bonus Action remains available for another feature. Nick does not automatically add the ability modifier to the extra attack's damage. That remains governed by the applicable Light weapon and fighting-style rules. Nor does making several attacks through Extra Attack let Nick trigger again and again. If a feat grants a different Bonus Action attack, adjudicate that independently rather than pretending Nick generated two Light-property attacks. Rules reference: D&D 5e SRD 5.2.1 — Light weapon property and Nick weapon mastery.

The 2024 D&D 5e Exhaustion system is easier to apply consistently than the 2014 version because its consequences follow a more uniform progression. This can make Exhaustion a more manageable source of accumulating pressure, although whether it improves actual play depends on how frequently the DM uses it.

The 2014 rules applied different penalties at successive levels, including disadvantages, reduced movement, and restrictions that could sharply impair a character. The 2024 rules instead use cumulative penalties to D20 Tests and Speed, with death at the maximum Exhaustion level.

This changes how players evaluate risk. The consequences are more predictable, but incremental penalties can still significantly affect combat, exploration, and attempts to recover from dangerous situations.

Use Exhaustion when the fiction supports cumulative strain: prolonged exposure, extraordinary exertion, or hazardous environments. Make its causes and recovery opportunities clear enough for players to judge their choices.

Avoid applying it automatically to every inconvenience. Its value comes from creating decisions about whether to continue, retreat, rest, or accept additional consequences.

The revised mechanics simplify administration; they do not establish that every campaign should feature Exhaustion more frequently.

In the current D&D 5e rules, equipping or removing a Shield requires the Utilize action. That means it is not simply the free weapon draw-or-stow interaction that can accompany an attack, and a character normally cannot gain or shed the Shield’s Armor Class benefit in the middle of another action without some feature that changes the action requirement.

This matters because the armor table itself can look misleading if you are searching only for the old “don” and “doff” times. Shields are handled separately from the minute-based times used for body armor. In practical terms, a creature spends its action to put the Shield into use, then benefits from it while properly equipped; removing it likewise costs the relevant action.

When switching between a two-handed weapon and sword-and-board tactics, account for that action cost before the turn begins. A character can still change weapons more freely under the current equipment rules, but the Shield is deliberately less fluid because its defensive benefit is substantial.

Rules reference: D&D 5e SRD 5.2.1 — Armor and Shields; Utilize action.

One minute in D&D 5e corresponds to about ten combat rounds because a round represents roughly six seconds in the game world. Therefore, an effect with a duration of 1 minute can usually remain active across ten rounds of combat if nothing ends it early.

That does not mean one creature receives ten uninterrupted turns. A round contains the turns of all participants in initiative order, and those turns represent activity occurring within the same approximate six-second span. After ten rounds have passed, about one minute of in-world time has elapsed.

For effects whose duration or ending point depends on a creature’s turn, follow the specific wording of the effect. “Until the start of your next turn,” “until the end of your next turn,” and “for 1 minute” are different timing instructions and should not be treated interchangeably. Concentration, incapacitation, dismissal, or another stated ending condition can also end an effect before its nominal duration expires.

Outside combat, the six-second structure is usually unnecessary. Treat one minute as ordinary fictional time unless exact timing becomes important enough to enter rounds.

Describe the fiction first, then state the mechanical effect clearly once it matters to a player's decision. “Your legs give way and you hit the floor—you are Prone” preserves atmosphere while ensuring the player understands the game state they are expected to act within.

Mystery can surround the cause, duration, or cure, but avoid hiding a known condition after the character has already paid for not understanding it. If the player must choose whether to move, attack, retreat, or spend a resource, give them the information their character could reasonably recognize. Uncertainty should create decisions, not turn familiar rules terminology into a guessing game.

Be especially clear when a house rule changes a standard effect. If a condition works differently in this campaign, communicate that before the difference determines a major outcome. Surprise should come from the situation, not from discovering that a familiar term secretly meant something else.

For complex effects, summarize the actionable parts: what the condition prevents, when another save occurs, and what can end it if that is known. Good description and precise mechanics reinforce each other rather than compete.

A shield and a two-weapon setup trade reliability in different directions: the shield improves your defense every time an attack targets Armor Class, while the second weapon is valuable only on turns when you can actually turn that hand into useful offense. The better choice therefore depends on how often you are attacked, how crowded your action economy is, and what the encounter asks you to do.

A shield is strongest when staying upright matters more than squeezing extra damage from a favorable round. It keeps paying off while you are restrained by positioning, forced to Dash, protecting an ally, or unable to reach the ideal target. Two weapons become more attractive when your build has features that reward additional attacks, when you can keep both weapons relevant, or when different weapon properties create tactical choices.

Do not compare only average damage on an empty battlefield. Ask what happens when you need a free hand, must switch targets, cannot close distance, or spend part of the turn on another task. A weapon style is good when its advantages survive real encounter friction, not only when every round follows the ideal rotation.

Weapon Mastery properties help martial characters most by adding decisions to attacks that would otherwise be mechanically similar. Their value is not only extra damage. Different weapons can influence movement, target choice, follow-up attacks, control, or the reliability of a particular tactic, which makes the weapon itself part of the turn’s planning.

That is a real improvement when the battlefield gives those distinctions something to interact with. A mastery effect matters more when enemies use cover, form lines, threaten vulnerable allies, or create reasons to move. In a featureless room where everyone stands still and trades attacks, many of the choices collapse back into damage optimization.

They also have limits. Masteries do not automatically solve every long-standing difference between martial and spellcasting characters, especially outside combat. They can also encourage weapon switching that some players enjoy and others experience as equipment bookkeeping.

The best way to judge the subsystem is therefore not “Did martial damage become high enough?” Ask whether martial turns now contain more readable choices, whether different weapons support genuinely different plans, and whether those choices remain useful across several kinds of encounter rather than only inside one optimized attack sequence.

A natural 1 on an attack roll in D&D 5e is an automatic miss, regardless of the attacker's modifiers or the target's Armor Class. It does not automatically cause a weapon to break, an ally to be struck, or the attacker to suffer some additional accident. Those consequences would require a separate rule or an explicitly adopted house rule.

This distinction matters because critical hits and critical failures are not symmetrical systems. A natural 20 on an attack roll produces a Critical Hit, while a natural 1 simply fails to hit under the standard attack rules.

A DM can still describe the miss dramatically. The attacker might overextend, strike a shield at an awkward angle, or lose a momentary opportunity. Such descriptions need not impose mechanical disadvantages.

Additional critical-fumble tables can be introduced as homebrew, but their frequency deserves consideration. Characters making multiple attacks have more opportunities to roll a natural 1, potentially making experienced martial characters disproportionately vulnerable to mishaps.

If the table wants cinematic accidents, consider using occasional narrative complications without automatically adding damage, lost turns, or equipment destruction.

Keeping the mechanical result clear allows the DM to narrate failures creatively without unintentionally changing combat balance.

Rules reference: D&D 5e SRD 5.2.1 — Attack Rolls.

The handaxe buys flexibility of range and handling; the battleaxe buys a larger damage die and a two-handed option. Under the current rules, a handaxe deals 1d6 Slashing and is Light and Thrown at 20/60.

A battleaxe deals 1d8 Slashing and is Versatile, dealing 1d10 when used two-handed for a melee attack. Between a hand axe and a battle axe, the practical question is therefore which problems you expect to solve. The handaxe is better when you want to switch from melee to short range without changing weapons or participate in Light-weapon fighting. The battleaxe is better when you want a stronger basic hit and the ability to shift between one and two hands.

They also have different mastery properties for characters able to use them: the handaxe has Vex and the battleaxe has Topple. That can matter more than one average point of damage. Choosing a weapon for the decisions it creates usually makes a bigger difference than comparing die sizes alone.

Rules reference: D&D 5e SRD 5.2.1 — Handaxe and Battleaxe weapon entries and their weapon mastery properties.

The penalty follows the type of attack, not whether the projectile happens to be an arrow. When you make a ranged attack roll with a weapon, spell, or other means, you have Disadvantage if you are within 5 feet of an enemy who can see you and is not Incapacitated.

Fire Bolt makes a ranged spell attack, so it falls under that rule. The cleanest way around disadvantage in close combat is changing position before attacking. Move away when doing so is safe, use a movement or teleportation option available to your character, have an ally control the nearby enemy, or choose an effect that does not require a ranged attack roll.

Remember that leaving an enemy's reach can provoke an Opportunity Attack unless a rule prevents it, such as taking the Disengage action. Tactically, this makes distance meaningful for spellcasters. It is not merely an abstract penalty: an enemy that reaches your comfortable space changes which options are efficient and forces the party to think about lines, cover, and protection.

Rules reference: D&D 5e SRD 5.2.1 — Ranged Attacks, Opportunity Attacks, and the Disengage action.

Under SRD 5.2.1, a player using the Ready action chooses a perceivable circumstance that will trigger their Reaction and then chooses the action or movement they will take in response. The rule does not provide a separate complexity limit for the trigger, so a DM can adjudicate detailed wording, but the trigger still needs to function as a perceivable circumstance rather than a private decision tree.

At the table, increasingly elaborate “if/then” conditions create two costs. They take longer to formulate, and they make it easier for everyone to disagree about whether the exact trigger occurred. A practical convention is to require one observable event and one declared response: “If the cultist starts casting a spell, I shoot,” or “If the ogre enters the doorway, I move behind the pillar.”

If a player wants several exceptions, priorities, or fallback clauses, ask them to simplify to the condition that actually matters. This preserves tactical intent without turning the Ready action into programmable logic. The character can also ignore the trigger when it occurs, so the wording does not need to anticipate every undesirable case.

Rules reference: D&D 5e SRD 5.2.1 — Ready [Action].

A horse is a mount in D&D 5e, not a vehicle. A cart, carriage, chariot, sled, or wagon pulled by that horse is the vehicle. Keeping those categories separate matters because mounted-combat rules apply to the creature being ridden, while equipment and travel rules can treat the thing it pulls as a vehicle.

Under the 2024 SRD, a willing creature can serve as a mount when it is at least one size larger than the rider and has appropriate anatomy. The rules then distinguish controlled and independent mounts during combat. The equipment section separately lists common mounts such as horses and gives carrying information for vehicles such as carts and wagons.

A horse can therefore participate in two related roles at once: it can be the creature providing locomotion and, when harnessed, the animal pulling a vehicle. The wagon does not become the mount merely because the characters are riding inside it. When an effect refers specifically to a mount, apply it to the qualifying creature; when it refers to a vehicle, use the vehicle entry and any relevant rules for that object.

Rules reference: D&D 5e SRD 5.2.1 — Mounted Combat; Equipment: Mounts and Vehicles.

Being airborne after a jump does not create a special “apex phase” in which a character automatically gains an extra opportunity to act. Jumping is movement, and actions or Bonus Actions can normally be taken at points during a turn when the character still has them available, but falling has its own timing once the character is no longer supported.

The practical ruling is to decide what the character is trying to do before resolving the movement past the point of support. If the character jumps beside a ledge and wants to attack, interact with something, or use an available feature during that movement, the DM can determine whether the action can occur at that position under the ordinary turn sequence. The jump itself does not grant priority over falling.

Reactions are different because a feature can specify its own trigger. Feather Fall, for example, is designed to react to a creature beginning to fall; that does not imply that every Action or Bonus Action can be inserted at the same moment.

Because the precise boundary between jump movement and the start of a fall is not completely spelled out for every unusual case, establish the intended action and position first, then use a consistent ruling rather than treating the top of every jump as a free timing window.

The SRD does not give a special rule that forbids a flying creature from carrying another character. The relevant limits are the creature’s carrying capacity and the rules for whatever effect provides the flying Speed. If the carried creature and its equipment fit within the flyer’s capacity, ordinary carrying rules provide the clearest baseline.

SRD 5.2.1 determines carrying capacity from size and Strength. For a Small or Medium creature, the normal maximum carried weight is Strength × 7.5 kg, with larger sizes increasing that limit. The flying rules separately say that a flying creature falls if it is Prone or Incapacitated or if its flying Speed becomes 0, unless it can Hover.

What the SRD does not spell out is a dedicated procedure for picking up, holding, or transporting a willing creature in flight. That leaves questions such as how many hands are required, whether the passenger can fight normally, and when a check is appropriate to DM adjudication.

Use weight as the hard baseline, then rule the physical handling consistently from the fiction. Do not add a penalty merely because flight is involved unless the situation creates an actual difficulty.

Rules reference: D&D 5e SRD 5.2.1 — Carrying Capacity, Flying, and Flying Speed.

Yes. The Giant Octopus's Tentacles attack contains no restriction preventing it from attacking a creature that is already grappled by those tentacles. The attack deals damage and, against a Medium or smaller target, also imposes Grappled and Restrained through the tentacles.

Nothing in that action says the attack becomes unavailable while the grapple is being maintained. That matters because the Giant Octopus is not using a player character's generic grappling procedure and reserving a particular hand. Its stat block directly defines what Tentacles does. If it hits the same target again, apply the attack's damage; the existing grapple simply continues unless something ends it.

I would not add a prohibition solely because the description says “all eight tentacles” are involved in the grapple, since the stat block does not turn that description into an action limitation. The fiction can describe the octopus tightening, repositioning, crushing, or striking with the same mass of tentacles while the mechanical procedure remains the one printed in the attack.

Rules reference: D&D 5e SRD 5.2.1 — Giant Octopus stat block and the Grappled condition.

Yes. In current D&D 5e, the Ready action lets a character choose a perceivable trigger and decide what action or movement will happen in response. When that trigger occurs, the character may take the Reaction immediately after the trigger finishes or ignore it.

That means a trigger can be phrased so the character sees the triggering event resolve before deciding whether to react.

The limitation is that Ready does not normally interrupt the trigger midway through unless another rule specifically says it does. “When the ogre attacks the wizard” therefore resolves differently from a rule that explicitly triggers when an attack is declared or before a result is known. The trigger should describe something the character can actually perceive rather than hidden game-state information.

If the readied action is casting a spell, the spell is cast when Readied and then held with Concentration until the trigger occurs; losing Concentration wastes it. That makes waiting for perfect information carry a real cost.

Use precise fictional triggers and resolve them in order rather than treating Ready as a general permission to rewind after seeing an outcome.

Rules reference: D&D 5e SRD 5.2.1 — Ready; Concentration.

The Stunned condition in D&D 5e ordinarily causes a creature to fail Strength and Dexterity saving throws automatically. Therefore, an effect that requires a Dexterity saving throw to end Stunned creates an important rules interaction: the creature may be unable to succeed unless the effect establishes a specific exception.

First read the ability's entire description. The saving throw that initially resists a stunning effect need not be the same type of saving throw used to recover from it. An initial Dexterity save might represent avoiding an attack, while a later Constitution or Wisdom save could represent recovering from its effects.

If the ability explicitly establishes an exception to the condition's usual consequences, apply the specific wording. Otherwise, do not assume that permission to repeat a Dexterity save automatically cancels the condition's normal saving-throw restriction.

For a custom monster, determine whether indefinite stunning was intentional. An effect with no practical recovery mechanism can become disproportionately dangerous, especially when several characters are affected simultaneously.

A straightforward design correction is to allow recovery through a saving throw not automatically failed by the condition, or to establish a clear exception in the ability's description. Explain the intended interaction consistently before resolving repeated attempts.

The Hide rules do not impose a special ban on trying again after failure, but a character can attempt to hide only when the circumstances actually allow the Hide action. A retry is therefore not an automatic right to keep rolling the same check until the die eventually shows 15.

Under the current rule, hiding requires appropriate concealment and being out of an enemy's line of sight. The character makes a DC 15 Dexterity (Stealth) check; on a success, the character has the Invisible condition while hidden. The Hide rule also defines ways that state ends, including making a sound louder than a whisper, being found by an enemy, making an attack roll, or casting a spell with a Verbal component.

Nothing there makes mundane hiding magical transparency. Invisible is the rules package used to represent being concealed: it affects being seen and attacks while the creature remains hidden. The fiction still matters when determining whether hiding can begin and whether an enemy can find the character.

For repeated attempts, ask whether another meaningful attempt has occurred. If the character moves to new cover, waits for a patrol to turn, creates a distraction, or spends another pressured turn trying, another check can make sense. If nothing changes and there is no cost for failure, repeated d20 rolls add no decision. Resolve the effort once, advance time or circumstances, or allow an inevitable success when failure has no remaining consequence. That prevents Stealth from becoming a pre-dungeon ritual of rolling until everyone has an acceptable number.

“Surprise” is normally established when combat begins; it is not a general condition that can simply be applied again to creatures already participating in the same fight. If a new creature suddenly enters an ongoing combat, the exact mechanical treatment depends on the D&D 5e rules version and how the DM resolves initiative and awareness.

Do not use the word “surprised” as a shortcut for every unexpected event. An unseen attacker, hidden reinforcement, sudden environmental change, or concealed ability may already be handled through positioning, visibility, advantage, initiative, or another specific rule. The fiction can still be surprising without creating a second full surprise procedure.

For reinforcements, decide when they become perceptible and place them into initiative using the procedure appropriate to the campaign’s rules. Characters who could not see or hear them may be unable to react to particular actions for ordinary reasons, but that is different from automatically reapplying start-of-combat surprise.

Review required: 2014 and 2024 D&D 5e handle Surprise differently, and the source question does not specify which rules set is intended. Exact initiative and Surprise wording should be verified before publication.

Yes. A controlled mount is a separate creature with its own Speed, movement, and limited action choices; its movement is not a shared pool with the rider's movement. The controlled mount acts on the rider's turn as directed and can take only Dash, Disengage, or Dodge as its action.

If the mount Dashes, that increases the distance the mount can move using the mount's Speed. It does not spend the rider's action or turn the rider's Speed into part of the mount's movement. The rider is being carried while the mount moves.

Mounting or dismounting is where the rider's own movement is spent. Doing either during the rider's move costs an amount of movement equal to half the rider's Speed. After dismounting, the rider can use whatever personal movement remains. If the rider still has an action available, the rider can also take the Dash action normally; the mount having already Dashed does not prevent that, because the two creatures have separate actions.

For example, a character with Speed 30 who dismounts spends 15 feet of personal movement on the dismount. The distance the mount already carried that character does not subtract from the remaining 15 feet. Keeping those resources separate resolves most mounted-combat confusion: track what the mount has spent, what the rider has spent, and the movement cost of getting on or off.

On a critical hit, the damage dice that belong to the attack are rolled twice; static modifiers are not doubled. Divine Smite is cast immediately after a qualifying hit and adds Radiant damage to that attack, so the smite dice are part of the critical hit’s doubled damage dice.

That means a “Divine Smite crit” should be resolved by determining the smite damage for the slot you used, including any extra die that applies because of the target’s creature type, and then rolling those damage dice twice along with the weapon’s damage dice. The fact that you decide to cast the spell after the hit is important because you already know whether the hit was critical before spending the slot.

The multiclass combination does not change that interaction by itself. The practical table check is simple: separate dice from modifiers. Dice that are damage from the attack get doubled on the crit; fixed bonuses stay fixed. If someone at the table remembers a different version, make sure everyone is looking at the same rules version before arguing the example.

Rules reference: D&D 5e SRD 5.2.1 — Critical Hits and the Divine Smite spell.

Passing through a creature’s space does not itself create a new exception for line of sight or Opportunity Attacks. Those are separate rules. An Opportunity Attack is triggered when a creature you can see leaves your reach using its movement, action, Bonus Action, Reaction, or one of its speeds; merely crossing an occupied space is not the trigger.

With three characters standing in a line, creatures can still matter for ranged attacks because another creature can provide cover when it obscures enough of the target from the attack’s point of origin. That depends on the actual geometry at that moment, not simply on two creatures sharing or crossing a square.

The trait that lets the swarm move through those spaces should do exactly what it says and no more. I would not infer that it also breaks sight, grants immunity to Opportunity Attacks, or creates Total Cover unless another rule says so. Resolve the movement step by step, then check reach, visibility, and cover from each relevant position.

Yes. A monster with the Incapacitated condition cannot take Legendary Actions in D&D 5e. The monster rules state this explicitly: a monster cannot take a Legendary Action while it is Incapacitated or otherwise unable to take actions.

That direct rule matters because Legendary Actions happen outside the monster’s normal turn and could otherwise look like a separate category that escapes the condition. They do not. The Incapacitated condition already prevents actions, Bonus Actions, and Reactions, and the Legendary Actions rules add their own specific restriction tying these off-turn actions to the monster’s ability to act.

At the table, once a creature becomes Incapacitated, remove its Legendary Actions from consideration until that condition ends. Do not spend or “hold” those uses while it is unable to act; the monster simply cannot take those actions during that period. If the condition ends later in the round, the creature can again use any Legendary Action uses it still has when an eligible trigger occurs.

This makes Incapacitated especially disruptive to monsters designed to remain active throughout the round, but it is the intended mechanical consequence of the condition.

Rules reference: D&D 5e SRD 5.2.1 — Incapacitated condition and Legendary Actions.

Flurry of Blows does not create one combined attack roll: it gives you multiple separate Unarmed Strikes, so any effect that applies to a single roll applies to only one of those attacks unless its own wording says otherwise.

The monk rule is clear on that point. Spending the resource for Flurry of Blows lets you make two Unarmed Strikes as a Bonus Action, and each strike has its own attack roll. What cannot be settled from the rules text available here is the exact Lucky feat wording being used at your table. Different versions of D&D 5e have used different text for similarly named options, and that wording decides whether the benefit modifies one d20 test, one attack, or something broader.

So the safe RAW procedure is: identify the exact Lucky text first, then apply it to each Flurry attack as a separate roll. If Lucky says it affects one roll or one d20 test, choose one strike. If it creates a broader duration or condition, follow that instead.

At the table, declare which strike receives the benefit before rolling it. That keeps the sequence unambiguous.

The Push weapon mastery in 2024 D&D 5e does not inherently turn movement into collision damage. Pushing a creature toward a wall is not the same event as causing it to fall, so the ordinary rules for falling damage should not automatically be applied to a horizontal collision.

Resolve the effect according to the mastery property's description. If an obstacle prevents the target from moving the full distance, distinguish the actual movement achieved from the distance the feature could otherwise have produced. A solid wall does not automatically transform unused movement into additional damage.

A DM may introduce a house rule for dangerous collisions, but its effects should be deliberate and consistent. Consider whether extra damage would occur on every push, only against particularly hazardous surfaces, or only when a separate environmental feature establishes a consequence.

Watch for repeated exploitation. Automatic damage from ordinary walls can substantially increase the value of forced movement, particularly when several attacks or effects can push the same target during one turn.

Existing environmental dangers may already supply appropriate consequences. A creature pushed into a fire, off a ledge, or through a damaging hazard should be adjudicated according to the relevant hazard rather than inventing a universal collision rule.

Under the current wording described in the source material, Tremorsense can pinpoint a creature within range when both creatures are in contact with the same surface or the same liquid; the detected creature does not need to keep moving. The movement qualifier applies to objects, not to creatures.

That means invisibility does not by itself prevent location from being detected through Tremorsense while the target remains on the shared surface. However, Tremorsense is not the same thing as sight. Knowing where a creature is located does not automatically mean every rule that requires seeing the target is satisfied.

The practical distinction is useful at the table. Describe Tremorsense as physical information carried through ground, walls, or liquid: pressure, vibration, displacement, or contact. A creature can therefore have its position revealed without becoming visually perceived.

Leaving the shared surface changes the situation. A creature in the air is outside what this sense is described as detecting through that surface. Because exact senses wording is version-sensitive, confirm the Tremorsense entry in the rules version your table is using before relying on this interaction for a consequential ruling.

A permanently blind player character should be handled by establishing exactly how the character perceives the environment and which consequences of the 2014 Blinded condition apply. The DM should not assume blindness grants compensating supernatural senses unless a specific feature or agreed house rule provides them.

Under the 2014 condition, sight-dependent ability checks fail automatically, the blinded creature has disadvantage on attack rolls, and attacks against it have advantage. These mechanical consequences make permanent blindness a substantial limitation, especially for characters whose abilities depend on visual targeting.

Discuss the intended character concept before play. A player may want to portray someone who navigates through training, hearing, touch, or magical assistance rather than someone continuously disadvantaged in every encounter.

Existing character abilities, equipment, spells, and alternative senses may provide legitimate ways to address some difficulties. Evaluate each independently instead of granting unrestricted blindsight by implication.

In exploration, provide sensory information the character could plausibly receive: footsteps, echoes, vibrations, air currents, smells, and changes in nearby movement. This preserves participation while maintaining meaningful distinctions between sight and other senses.

If the group adopts a compensating house rule, define its range, limitations, and interactions with invisibility, darkness, and visual spell requirements before play.

A creature with 10-foot reach can potentially grapple a character from beyond the range of ordinary melee attacks. Under the 2024 D&D 5e rules, the Grappled condition reduces the character's Speed to 0, preventing them from simply walking closer. However, being grappled does not prevent attacking, casting spells, or attempting to escape.

The most direct solution is to use an action to attempt escape, making a Strength (Athletics) or Dexterity (Acrobatics) check against the grapple's escape DC. A successful check ends the condition, allowing the character to move normally with any movement remaining.

Alternatively, the character can attack with a weapon or spell that reaches the grappler. A reach weapon may solve the distance problem, while ranged attacks and spells offer other options, subject to their normal restrictions. Teleportation and effects that move either creature beyond the grapple's permitted range may also break the hold.

The Dungeon Master should distinguish the distance between the creatures from their physical size and occupied spaces. A long-reaching appendage does not automatically place the grappler within five feet of its victim. The encounter becomes more interesting when players understand these spatial constraints and can choose among escaping, attacking, repositioning, or requesting assistance.

Rules reference: D&D 5e SRD 5.2.1 — Grappled condition.

D&D 5e does not support treating every attempt to snatch a held item as an ordinary free object interaction. If another creature is actively holding or controlling the object, the DM should use a rule that actually covers forced possession changes, or make an explicit ruling rather than letting the attacker simply take it automatically.

First distinguish three cases. An unattended object can usually be picked up through the normal object-interaction rules. An object carried but not actively defended may call for an ability check if access is uncertain. An object held in combat is different: taking it should normally require an action and opposition because the defender is actively resisting.

If the rules version or optional material at the table includes a disarm procedure, use that procedure consistently. If not, a simple ruling can use a contested check chosen from the fiction—for example, force against force, or quick hands against the defender’s ability to retain the item. State the cost and consequence before the roll.

Do not let an improvised ruling become a universal superior attack option. If stealing a weapon is easier than attacking, grappling, or using dedicated features, it will distort combat.

The exact RAW procedure should be checked against the rule set and optional rules your table uses before publication.

Its best creative use is turning a melee tool into an immediate short-range option without forcing you to change ability scores or equipment. The handaxe has a 20/60 range, and its throwing feature also lets you draw the weapon as part of the attack.

That creates useful small decisions: hit an enemy across an obstacle, finish a threat that is withdrawing, stay outside a hazardous area for one turn, or throw another weapon when your melee position collapses. Because the handaxe is also Light, it can participate in two-weapon arrangements when the other requirements of that property are met. Outside a fight, I would be more cautious.

Throwing it to cut a rope, trigger a mechanism, or bury it in wood is not an automatic effect granted by the rule; it is a fictional action for the GM to resolve according to the situation. That distinction is useful. The property guarantees a ranged attack, while improvised applications can still be excellent ideas without becoming universal powers of the item.

Rules reference: D&D 5e SRD 5.2.1 — Weapons: Handaxe; Thrown property.

You only get one Bonus Action on your turn, so if both your goblin Hide option and an Illusionist feature let you do something as a Bonus Action, you must choose between them that turn. You cannot use both unless another rule explicitly gives you an additional Bonus Action.

The general Hide rule is also important. A successful Hide gives you the Invisible condition while you remain hidden, but you stop being hidden after a sufficiently loud noise, being detected, making an attack roll, or casting a spell with a Verbal component. A subclass feature can create an exception to that general rule, but its exact wording controls the exception.

That means a sequence such as “cast Silent Image, use Minor Illusion as a Bonus Action, then Hide as another Bonus Action” is not legal under the normal action economy. Instead, decide which Bonus Action matters most on that turn.

The remaining interactions need the exact feature and spell text being used. In particular, telepathic communication does not automatically erase a summon’s command requirements, and the available rules text here does not establish the goblin species feature or the Illusionist feature described. Keep those entries open at the table and follow their precise wording rather than extending them by implication.

The 2024 SRD places darkness, heavy fog, and dense foliage under the same Heavily Obscured rules category for many purposes: a creature is effectively Blinded when trying to see something in that obscured space. The text therefore gives them the same mechanical label even though their real-world optical behavior is different.

That shared category cleanly handles trying to perceive a creature inside the obscured area. The awkward edge case is looking through an intervening area of darkness toward something illuminated beyond it. Fog is physically opaque, while ordinary darkness is an absence of light, but the SRD wording also describes a Heavily Obscured area as opaque. The supplied rule text does not separately spell out a transparent-darkness exception for that line-of-sight situation.

For play, choose one interpretation and state it consistently. A literal category-based reading can treat both as blocking sight through the area; a simulation-oriented ruling can distinguish darkness from fog when the target beyond is illuminated. Because that distinction is not explicitly resolved in the retrieved SRD wording, it is better presented as a table ruling than as a certainty the rules unambiguously settle.

Rules reference: D&D 5e SRD 5.2.1 — Vision and Light: Obscured Areas.

The interaction between Mage Slayer and Shield depends on which edition of the D&D 5e rules is being used. The 2014 and 2024 versions of Mage Slayer are substantially different, so a ruling based on one version should not be transferred to the other.

Under the 2014 feat, Mage Slayer can allow a reaction melee attack when a nearby creature casts a spell. Shield is itself a spell cast as a Reaction, meaning its casting can potentially satisfy that trigger when the relevant positional and reaction requirements are met.

However, the Mage Slayer attack does not automatically prevent Shield from taking effect. The defensive spell's increased Armor Class must be considered when resolving attacks to which that protection applies. The precise sequence matters because Shield is triggered by an attack, while Mage Slayer responds to spellcasting.

The 2024 Mage Slayer feat no longer grants the same nearby-spellcasting reaction attack, so the corresponding 2014 interaction does not carry over.

At the table, establish the rules version first, identify which creature has an available Reaction, and resolve each triggering event in order.

Do not conflate Mage Slayer with Counterspell: an additional attack is not automatically a spell interruption.

In D&D 5e, massive damage needs careful terminology: the ordinary instant-death rule and the optional massive-damage procedure are different mechanics. The first concerns a blow that drives a character to zero hit points with enough damage remaining to kill them outright. The second is an optional way to make particularly heavy single hits cause additional shock or injury.

Under the basic instant-death procedure, compare the damage remaining after a character reaches zero hit points with that character's hit point maximum. If the remainder meets or exceeds the maximum, the character dies rather than beginning death saving throws. Ordinary high damage does not automatically trigger the optional shock procedure.

The 2014 Dungeon Master's Guide also presents an optional massive-damage approach based on a single substantial hit. A table choosing that option should check its exact trigger, saving throw, and outcomes in the edition being used; it should not assume the procedure is automatically part of every D&D 5e game.

Before adopting extra injury consequences, assess how they affect front-line characters, low-hit-point parties, and encounters with large individual attacks. Explain the option to players beforehand and apply it consistently to comparable situations.

A thrown handaxe continues to use the same ability modifier you would use for a melee attack with it. Because it is a melee weapon with the Thrown property, that modifier applies to both the attack roll and the damage roll.

For a hand axe when thrown, the base damage is 1d6 Slashing and its range is 20/60 feet. Within normal range you attack without the penalty associated with long range; beyond 20 feet and up to 60, the attack roll has Disadvantage. A higher Strength modifier therefore improves two important things at once: the chance to hit and the damage dealt when the attack lands.

That makes the handaxe particularly useful for a Strength-focused character who needs to reach an enemy without switching to a weapon based on another ability. Fictionally, it also preserves a nice continuity: the same physical force drives the close strike and the throw, while only the distance and risk of missing change.

Rules reference: D&D 5e SRD 5.2.1 — Handaxe weapon entry and the Thrown weapon property.

The 2024 Paladin creates real Bonus Action competition between two signature tools. In SRD 5.2.1, Lay On Hands is used as a Bonus Action, and Divine Smite is a Bonus Action taken immediately after a qualifying hit. A Paladin therefore cannot use both on the same turn because a creature only gets one Bonus Action on its turn.

That restriction has a clear benefit: smiting now occupies action economy instead of being an extra resource spend layered freely onto attacks. It limits how much burst damage can be stacked into one turn and makes other Bonus Action options compete with damage.

The cost is that some combinations that feel thematically natural are blocked by the same action slot. Healing an ally and then landing a critical hit is a good example: the Paladin has already committed the Bonus Action, so the later hit cannot trigger Divine Smite that turn.

Whether that feels healthier or clunkier depends on the decisions it produces. If the player is choosing between genuinely different tactical priorities, the competition has value. If the recurring experience is simply that one iconic Paladin feature prevents another iconic feature from functioning, the friction will be much more noticeable.

Rules reference: D&D 5e SRD 5.2.1 — Lay On Hands; Paladin's Smite; Divine Smite.

Nick changes the timing of the extra attack associated with the Light weapon property; it does not independently grant unlimited attacks or remove a Hand Crossbow's ammunition requirements. The interaction therefore depends on the weapons involved, the order of attacks, and the character's available hands.

Under the 2024 rules, the extra attack from the Light property is normally made using a Bonus Action. Nick allows that additional attack to occur as part of the Attack action when the relevant weapon mastery conditions are satisfied. It does not eliminate the requirement to qualify for that extra attack in the first place.

A Hand Crossbow introduces another consideration: ammunition must be loaded according to its weapon properties. Holding another weapon can complicate that process because the character may need a free hand for loading, even when a feature alters other limitations on crossbow attacks.

Check the exact sequence of attacks, which weapon possesses Nick, whether the character has the necessary mastery, and whether any feat modifies the normal restrictions.

Avoid conflating the ability to attack with two weapons, the timing of a Light-property attack, and the ability to reload a crossbow. These are separate mechanical questions.

There is no general SRD rule that every monster must resolve the attacks in a Multiattack entry in the printed left-to-right order. The specific wording of that monster’s Multiattack action controls what attacks it can make and whether the text imposes any sequence or condition.

If the entry says the monster makes several attacks “using” listed attacks in any combination, the flexibility is explicit. If it says the monster makes one attack of one type and one of another, it establishes the required components but does not by itself create a universal sequencing rule. A stat block can still impose an order through explicit wording or through an effect that depends on an earlier result.

When timing matters, read the whole action rather than inferring a rule from formatting. Resolve any explicit prerequisites, “then” clauses, replacements, or conditional effects exactly as written. Otherwise, choose an order that satisfies the listed attacks.

The important point is that Multiattack is a monster action defined by its own stat block, not a general player-style Extra Attack sequence.

Rules reference: D&D 5e SRD 5.2.1 — monster stat blocks, Multiattack.

Carrying several weapons is worthwhile only when the weapons create different decisions. If every option solves the same problem with nearly the same reach, damage, and tactical role, a large arsenal becomes inventory rather than gameplay. The useful question is not “how many weapons can I carry?” but “what situation would make me sincerely choose this one instead of my default?”

A compact loadout can cover several kinds of problem: one weapon for reach, one for throwing or ranged pressure, one that works well in confined spaces, or one whose properties interact differently with your character’s features. Current D&D 5e also gives some characters reasons to care about weapon-specific mastery effects, which can make changing weapons more meaningful than it was in a simpler damage-die comparison.

Do not build a golf bag around hypothetical edge cases. Pick two or three alternatives and name the scenes where each earns its place. If one option would only leave the sheath once every twenty sessions, it is probably flavor or backup equipment rather than a tactical tool. A useful arsenal gives you distinct answers to recurring problems without turning every combat turn into equipment bookkeeping.

A player can ask for a character's story to end in death, but that is a table agreement, not a general rules option that replaces the normal death procedure. Under the standard rules, a character reduced to 0 hit points may die instantly in specific circumstances or otherwise falls unconscious and begins making death saving throws. Three failed death saves mean death; the rules do not add a universal “choose to die” button.

As a DM, separate narrative intent from mechanical advantage. If a player wants a fitting final scene because they are finished with the character, agreeing to a deliberate death can be perfectly workable. Decide together whether it happens immediately, after the current danger resolves, or through a final action that makes sense in the fiction.

Be more cautious if choosing death would bypass consequences, transfer resources, trigger abilities, or materially change a combat. In that case, keep the ordinary mechanics unless the whole table understands the exception.

The important part is that the death still belongs to the fiction. Give it causes, witnesses, and consequences rather than treating the character sheet as something the player simply switches off.

Keep the SRD fall rule as the baseline, then add at most one lightweight modifier for unusual landing conditions. D&D 5e already abstracts falling as 1d6 Bludgeoning damage per 10 feet fallen, to a maximum of 20d6, and the creature normally lands Prone if it takes damage.

That rule intentionally does not model mass, acceleration, body orientation, or terminal velocity. Trying to derive every fall from real physics creates false precision because the rest of the combat system remains abstract. If the desired feeling is “the environment matters,” model that directly instead.

For example, classify the landing as forgiving, normal, or hazardous. Deep liquid, a steep slope, or something that collapses under impact might reduce the consequence; jagged rock, spikes, or machinery might add a separate hazard. The SRD already gives falling into water a specific reaction-based chance to halve fall damage, so do not overwrite that rule accidentally.

Rules reference: D&D 5e SRD 5.2.1 — Falling.

Use the listed average for most monsters and roll when variation itself adds something to the encounter. Both methods are supported: the SRD presents a fixed hit-point number and the monster’s Hit Dice formula, and tells the GM to use either the number or the roll, not both.

Average hit points make preparation faster and encounter durability more predictable. That is especially useful for routine enemies, large groups, or fights whose pacing depends on a rough length. Rolled hit points make otherwise identical creatures less uniform and can create uncertainty for players who know monster statistics well.

If you roll, do it before the session rather than pausing combat. Record the totals next to each creature. Avoid secretly switching between rolled and average hit points during the fight to keep a monster alive or make it die sooner; that changes the method from randomization into invisible encounter tuning.

A useful compromise is average hit points for ordinary creatures and rolled totals for a few individuals you want to feel distinct. The choice is mostly about pacing and texture, not about one method being more correct.

Rules reference: D&D 5e SRD 5.2.1 — Monster Stat Blocks: Hit Points.

Use Surprise when an unexpected event is the start of combat, not as a general rule for every sudden source of damage. In current 5e, a creature surprised by the start of combat has Disadvantage on its Initiative roll.

If the barmaid suddenly swings at a character and the order of reactions matters, begin combat before resolving the attack. Roll Initiative, apply Surprise to anyone genuinely caught unaware, and let the sequence determine whether the strike happens before someone can act. Do not grant a free attack and then roll Initiative unless a specific rule says to do that.

A spooked horse kicking once can instead be treated as a hazard if nobody is trying to enter a continuing fight. In that case, the DM can call for an appropriate saving throw and resolve the consequence without starting combat. The same can apply to a trapped animal lashing out as an immediate hazard.

The dividing question is whether several creatures now have competing intentions whose order matters. If the answer is yes, Initiative gives the scene a fair sequence even if combat ends after one round. If the event is a single environmental consequence and nobody continues hostilities, a hazard resolution is usually cleaner.

A natural 20 on an attack roll is the standard way to score a Critical Hit in the 2024 rules, but it is not the only one. Specific class features and conditions can either expand the range of rolls that count as critical hits or make a successful attack automatically critical.

The SRD Champion Fighter is a clear example of the first type: Improved Critical lets weapon and Unarmed Strike attack rolls score a Critical Hit on a 19 or 20, and Superior Critical later expands that range to 18–20. Conditions provide the second type. A creature with the Paralyzed or Unconscious condition suffers an automatic Critical Hit from an attack roll that hits when the attacker is within 5 feet.

These mechanisms should not be treated as interchangeable. An expanded critical range changes which d20 results score a critical. An automatic-critical rule still requires whatever the specific rule says must happen first, such as an attack hitting and the attacker being close enough.

When another feature appears to modify critical hits, read its exact wording rather than generalizing from these examples. Specific rules can create additional exceptions.

Rules reference: D&D 5e SRD 5.2.1 — Critical Hit; Champion Fighter: Improved Critical; Paralyzed and Unconscious conditions.

The mounted-combat rules do not say that a condition automatically makes a rider lose control of a mount. A controlled mount is controlled because it is trained to accept a rider; while controlled, it shares the rider’s Initiative and is limited to the actions the mounted-combat rules specify.

Prone has an explicit interaction with staying mounted. If you are knocked Prone while mounted, you must make the listed Dexterity saving throw or fall from the mount and land Prone nearby. The same kind of save is required if the mount is knocked Prone. That rule governs falling off; it does not itself say the mount becomes independent.

For other conditions, read the condition and any relevant feature literally. If an effect prevents actions, movement, speech, or perception, it may make giving meaningful direction difficult in the fiction, but that is not the same as a general RAW rule that “condition X ends control.” When the text does not specify the interaction, the GM may need to adjudicate what direction is physically possible.

Rules reference: D&D 5e SRD 5.2.1 — Mounted Combat; Prone condition.

Under the standard death-saving-throw procedure, a character starting from zero successes and zero failures has about a 59.5% chance to survive without outside help before accumulating three failures. Here, “survive” means either becoming Stable after three successes or rolling a natural 20 and regaining a Hit Point before dying.

The calculation must account for more than a simple race to three successes. On each d20, 10–19 produces one success, 2–9 produces one failure, a natural 1 produces two failures, and a natural 20 immediately restores a Hit Point. Because the natural 1 and natural 20 have asymmetric effects, treating each save as merely a 55% success versus 45% failure event gives the wrong result.

A state-by-state calculation from zero successes and zero failures gives a survival probability of 0.595125, or 59.5125%. The complementary probability of dying before stabilization or a natural 20 is 40.4875%.

This assumes no damage while unconscious, no healing, no features that modify or reroll the save, and no other creature stabilizing the character. Any of those can change the probability substantially.

Rules reference: D&D 5e SRD 5.2.1 — Dropping to 0 Hit Points: Death Saving Throws.

The Versatile property gives a battleaxe flexibility between using one hand and two. In SRD 5.2.1, a battleaxe deals 1d8 Slashing damage normally, and its Versatile value is 1d10 when you use it with two hands for a melee attack.

The tactical value is therefore not the two extra average points of maximum die size by themselves; it is preserving a free hand when that matters. With one hand, you can keep a Shield or another usable object available if your character can benefit from it. When the other hand is free and defense or utility from that hand is unnecessary, switching to two hands modestly improves the weapon’s damage.

Do not treat Versatile as a mandatory rotation. If your build depends on a Shield, grappling, a spellcasting setup, or another hand-held tool, the one-handed mode can be more valuable than the larger die. Conversely, when both hands are available, the two-handed option costs nothing beyond giving up that flexibility for the attack.

Rules reference: D&D 5e SRD 5.2.1 — Weapon Properties: Versatile; Battleaxe.

For a monster feature marked Recharge X–Y, roll 1d6 at the start of each of that monster's turns after the feature has been used. If the result falls within the listed range, the monster regains the use of the feature immediately and can use it again on that turn if its action economy allows. You do not make a recharge roll before the feature's first use.

For example, an action marked Recharge 5–6 can normally be used once. On each later turn, roll 1d6 at the start of the monster's turn; a 5 or 6 restores it, while 1–4 leaves it unavailable for that turn. The SRD also states that this kind of limited-use feature recharges when the monster finishes a Short or Long Rest.

Make the roll openly or secretly according to the table's normal procedure, but keep the timing consistent. Rolling at the end of the round or immediately after the ability is used changes the expected availability of the feature.

Rules reference: D&D 5e SRD 5.2.1 — Limited Usage: Recharge X-Y.

D&D 5e treats a shield as one abstract equipment category: the standard shield grants +2 AC rather than assigning separate defensive values to bucklers, round shields, kite shields, and similar forms. That keeps a common defensive choice mechanically simple, even though it sacrifices distinctions that matter in real weapon-and-armor use.

A DM can therefore describe very different shields without changing their statistics. A compact dueling shield, a battered infantry shield, and an ornate temple shield can all use the same rules if the difference is primarily visual or cultural. This preserves character expression without quietly creating a superior equipment option.

If the table wants shield types to matter mechanically, add trade-offs rather than simply increasing AC. A larger shield might impose a movement, Strength, hand-use, visibility, or carrying cost; a smaller one might trade some protection for easier handling. The important part is to define the whole exchange, because passive AC bonuses affect many attacks over an adventuring day and can become more valuable than they first appear.

Rules reference: D&D 5e SRD 5.2.1 — Equipment: Armor and Shield.

D&D combat Speed should not be read as a creature’s biological top sprinting speed. It is a tactical allowance used inside a round that also contains turning, attacking, reacting to threats, changing direction, handling equipment, and making other decisions. Converting that grid distance directly into “maximum miles per hour” produces misleading comparisons with real animals.

This matters especially for creatures such as horses, wolves, or big cats. Real sprinting measurements describe short bursts under favorable conditions. Combat movement represents controlled movement inside a dangerous, rapidly changing situation. Long-distance travel is handled by a different scale again, because endurance, terrain, rest, and group pace matter more than peak velocity.

For a DM, use the rule that matches the scene. Use combat Speed when positioning within an encounter matters. Use travel procedures for hours of movement. If the fiction depends on a chase, resolve the changing distance, obstacles, exhaustion, and choices instead of simply declaring that the creature with the larger combat Speed wins.

The abstraction is a feature, not an error. The game needs one manageable movement value for tactical play without pretending to model acceleration, stride length, fatigue, and maximum sprint performance for every creature.

A handaxe is attractive when flexibility matters more than the battleaxe’s larger damage die. In SRD 5.2.1, the handaxe is a simple 1d6 Slashing weapon with the Light and Thrown properties at 20/60 feet, while the battleaxe is a martial 1d8 Slashing weapon with Versatile 1d10. Characters with access to Weapon Mastery also get different mastery properties from the two weapons.

That means the handaxe can cover both melee and short-range attacks without changing to a different weapon, and its Light property can matter for builds using multiple light weapons. It is also available to characters who have simple-weapon proficiency but not full martial-weapon proficiency.

The battleaxe is better when you want a stronger basic melee hit and the flexibility to use one or two hands. Its larger die is valuable, but that advantage does not automatically outweigh a weapon that solves more kinds of positioning problem.

Choose according to the role the weapon plays in the character’s turns. If you expect to throw it, combine it with another light weapon, or need simple proficiency, the handaxe has a clear niche.

Rules reference: D&D 5e SRD 5.2.1 — Handaxe and Battleaxe weapon entries and their weapon properties.

When a monster ability says it moves up to a specified distance and makes an attack, the natural reading is to resolve the described movement before the attack. However, the wording does not necessarily require the creature to cover a positive distance, because moving up to a maximum permits choosing no movement.

For a Pounce action worded as movement of up to half the creature's Speed followed by one Rend attack, the straightforward procedure is to choose the movement distance, resolve that movement, and then make the attack if possible.

This differs from abilities that explicitly require a creature to move a minimum distance before gaining a particular benefit. A requirement such as moving at least 20 feet would establish a separate condition; merely saying up to half its Speed does not.

The question of voluntarily omitting the attack is less explicit. An action containing two stated effects does not automatically become a menu from which either effect can be selected independently. A DM may permit the creature to forgo the attack, but should distinguish that adjudication from a general permission established by the wording.

For consistency, apply the same interpretation to similarly structured monster actions and check whether the relevant stat block contains additional timing or movement restrictions.

A D&D 5e table can use square-grid movement and circular area templates consistently by treating movement distance and area geometry as separate procedures. The fact that diagonal movement may use a simplified square-counting rule does not automatically require circular spell effects to become square-shaped.

First establish how movement and weapon reach are measured. Some grid conventions count diagonal squares using the same cost as horizontal squares, producing results that differ from ordinary geometric distance. Then establish how circular areas are positioned and which squares count as affected.

A physical or digital circular template can provide a consistent visual reference. The DM must also apply the applicable edition's procedure for determining whether partially covered squares are included. Avoid importing a template rule from an older rulebook without checking whether the current edition uses the same procedure.

Difficult cases arise when a creature appears within weapon reach according to grid counting but outside the drawn boundary of an emanation. Resolve each measurement using its established procedure rather than silently changing one to match the other.

Agree on these conventions before a disputed interaction occurs. If the table wants geometric distance to govern every measurement, that is another possible approach, but it should be adopted consistently rather than introduced only when a particular spell or weapon produces an inconvenient result.

Choose one table ruling and state it before the tactic matters: either the monk can maintain the grapple at the feature’s extended reach, or the target must end up within the normal reach required to keep the grapple. Consistency matters more here than trying to disguise an ambiguous interaction as certain RAW.

For play, allowing the extended grapple is the more permissive interpretation and creates a distinctive control tool. Watch what it combines with: forced movement, hazards, flight, and repeated repositioning can make the extra reach much more valuable than the initial grapple suggests. If those combinations dominate encounters, narrow the ruling rather than changing it unpredictably from fight to fight.

The stricter ruling is easier to administer: the feature can help initiate an Unarmed Strike at range, but a grapple must be maintainable at ordinary reach once the strike resolves. If you use that approach, tell the monk player early so they do not build tactics around a different expectation.

Whichever ruling you choose, write it down in one sentence and apply the same logic to equivalent reach-changing effects. That turns a disputed edge case into a stable table rule.