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 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.

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 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.

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.

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. 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.

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.

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.

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.

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.

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.

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.