D&D 5e Spell Rules & Magic Interaction Questions for Dungeon Masters

No. “Magical Darkness” is not a fourth illumination category in SRD 5.2.1. The lighting categories are Bright Light, Dim Light, and Darkness; magical effects can create Darkness, and the particular effect tells you what extra properties apply.

This distinction matters because the Darkness spell does more than merely create the normal Darkness category. Its text says the magical Darkness fills a 15-foot-radius Sphere, Darkvision cannot see through it, and nonmagical light cannot illuminate it. Those restrictions come from the spell’s description.

Do not automatically copy those properties onto every supernatural effect that happens to create or mention magical darkness. If another spell, monster trait, or magic item creates Darkness, apply the rules that effect actually states together with the normal rules for Darkness.

Conversely, an ability can explicitly interact with magical Darkness. Devil’s Sight, for example, says the Warlock can see normally in Dim Light and Darkness whether magical or nonmagical.

Keeping the illumination category separate from effect-specific exceptions prevents one spell’s wording from silently becoming a universal rule.

Rules reference: D&D 5e SRD 5.2.1 — Darkness illumination category, the Darkness spell, and Devil’s Sight.

A normal grapple does not silence a spellcaster, but a DM can adjudicate a separate attempt to prevent the caster from speaking. The two rules should not be collapsed into one automatic effect.

Under the current rules, the Grappled condition restricts movement and affects certain attacks, but it does not say that the target cannot speak, provide spell components, or cast spells. A successful grapple therefore does not by itself stop Verbal components.

Separately, Verbal components must be spoken in a normal speaking voice, and a creature that is actually gagged cannot provide them. The rules do not provide a standard combat action called Cover a Creature's Mouth, so getting from Grappled to gagged requires DM adjudication.

If a player attempts it, treat it as an additional improvised action rather than a free benefit of the original grapple. Decide whether the attempt is physically plausible, require an appropriate resolution when the outcome is uncertain, and give the target a meaningful way to resist or break that control. Depending on the fiction, maintaining the gag may also occupy a hand or require a more complete restraint.

Success should prevent only what the fiction actually prevents. Stopping speech blocks spells with Verbal components; it does not automatically stop spells that require only Somatic or Material components. This keeps the tactic useful and intuitive without making every successful grapple an automatic shutdown of a spellcaster.

Wish can restore youth only if the DM allows it as an unlisted reality-altering effect; restoring youth is not one of the spell's guaranteed options. The spell explicitly permits a character to wish for something beyond its listed effects, but in that case the GM decides what happens, and the result can be partial, altered, or fail.

That distinction matters because there is no RAW procedure saying how many years are removed, whether maximum lifespan changes, or whether the character merely looks younger. Those details are adjudication, not a hidden standard effect. If the wish is granted, the caster also suffers Wish's normal stress for producing an effect other than duplicating a spell of level 8 or lower, including the chance of losing the ability to cast Wish again.

For a clean ruling, define the requested outcome before resolving it. “Return my body to the physical age of twenty-five while retaining my memories” is much easier to adjudicate than “make me young again.” Then decide whether the campaign treats aging as biological, magical, or partly supernatural.

If youth would erase an important curse, bargain, or adventure consequence, resolve that interaction explicitly rather than assuming Wish automatically overrides it.

Under the 2024 rules, a successfully countered Action spell normally does not stop you from casting a spell with your Bonus Action afterward, because Counterspell causes the interrupted spell's slot not to be expended. The 2014 rules work differently, so the edition matters.

The 2024 spellcasting restriction says that on a turn you can expend only one spell slot to cast a spell. Counterspell says that when it successfully interrupts a spell, the action used to cast that spell is wasted, but if the spell was cast with a spell slot, that slot is not expended. As a result, the failed casting has not used the turn's one permitted spell-slot expenditure. If the character still has a Bonus Action available, they can cast a Bonus Action spell and expend a slot for it. Normal casting requirements still apply.

This is different from saying that Counterspell rewinds the entire attempted casting. The Action is still gone; it is specifically the spell slot that is preserved, and the 2024 restriction is written around expending spell slots.

Under the 2014 rules, Bonus Action spellcasting uses a different restriction: after casting a Bonus Action spell, the only other spell allowed on that turn is a cantrip with a casting time of one Action. A countered leveled Action spell does not become a cantrip merely because it failed, so a later Bonus Action spell would not make that sequence legal.

For this interaction, always establish whether the table is using the 2014 or 2024 spellcasting rules before ruling on the turn.

No. Darkness plus Devil’s Sight can hinder allies, but the problem depends on placement and objectives rather than the combo being automatically bad. The Darkness spell creates magical darkness that normal Darkvision cannot see through, while Devil’s Sight lets the Warlock see normally through magical and nonmagical darkness within its range.

For creatures that cannot see through the area, the darkness is heavily obscuring. Attacking a target you cannot see gives Disadvantage, while attacking a creature that cannot see you gives Advantage, so two mutually blinded combatants can end up rolling normally. The larger cost is often lost targeting, positioning information, opportunity attacks, and spells or features that require sight.

Use the spell selectively. Place it over enemy archers or casters, cover a retreat, block a corridor, or carry the effect on an object that can be covered when allies need sight again. Avoid dropping it over the entire melee by default.

The combo is strongest when darkness creates a local problem for enemies while leaving allies’ preferred actions intact.

Rules reference: D&D 5e SRD 5.2.1 — Darkness, Devil’s Sight, and unseen attackers and targets.

Dream can be genuinely lethal to ordinary NPCs under the rules, but it is not an automatic long-range assassination effect.

The spell targets a creature the caster knows on the same plane. Its frightening version allows a short message and then calls for a Wisdom saving throw. On a failure, the target gains no benefit from the rest and takes 3d6 psychic damage when it wakes. That matters enormously against people who are not built like adventurers. A typical commoner has only 4 Hit Points, while a noble has 9, so a failed save can easily reduce either to 0. NPCs normally die at 0 Hit Points unless the DM chooses to treat a particular one like a player character.

That makes the spell especially useful for threats, extortion, punishment, and political terror. I would lean into those consequences rather than treating it as merely a strange combat option. Important people in a world where this magic exists may hide personal information, employ magical specialists, change sleeping arrangements, investigate patterns of dream attacks, or seek extraordinary protection once they realize what is happening.

Do not add protections merely to nullify a player who chooses the spell, though. Let its reach matter. The interesting response is a world that reacts to repeated supernatural attacks: frightened servants, suspicious courts, desperate counter-investigations, false accusations, and enemies trying to discover who the messenger is.

Also avoid granting perfect anonymity unless another rule establishes it. The spell describes what the messenger can do inside the dream; it does not create a general rule that nobody can identify or investigate the attacker.

No. The sensor created by Scrying is explicitly invisible and intangible, so it is not a physical object that creatures can grab, strike, block with a hand, or otherwise interact with by ordinary touch. If the target fails its saving throw, the sensor appears within 10 feet of the target, moves with that target, and lets the caster see and hear as though present there. A creature that can perceive the sensor sees it as a luminous orb about the size of a fist, but seeing it does not make it solid.

That distinction matters at the table. A character might notice the sensor through an effect that reveals it and then react to being watched, move somewhere protected from divination, dispel the magic if an applicable effect allows it, or use other anti-divination measures. What they cannot do merely because they can see it is swat the sensor away or put it in a box as though it were a normal object.

If another rule specifically says it can affect a magical sensor, follow that specific rule. Otherwise, treat the sensor as perceptible under the right circumstances but physically untouchable.

They share a spell level because both provide campaign-scale travel, but they solve different problems and are constrained in different ways. The rules do not give an official design explanation for why both are 7th level, so any rationale beyond their written effects is interpretation.

Teleport moves the caster and up to eight willing creatures to a destination on the same plane. Its reliability depends on how well the destination is known: an established teleportation circle or recently obtained associated object is extremely reliable, while unfamiliar or false destinations can produce errors or mishaps.

Plane Shift instead crosses between planes. It also carries up to eight willing creatures, but it requires a specially attuned fork worth at least 250 gp. Unless the caster knows a teleportation-circle sigil sequence on the destination plane, the spell only specifies a destination in general terms and the GM determines where the group actually appears nearby.

So the spells are not redundant. Teleport is the strong same-plane precision tool; Plane Shift grants access to an entirely different plane with a special material key and less exact arrival. Their equal level marks similar campaign-changing reach, not identical utility.

Yes: True Strike can trigger the Cleric's Divine Strike option of Blessed Strikes, because the cantrip makes an attack with a weapon and Divine Strike triggers when you hit with an attack roll using a weapon. It does not require you to take the Attack action.

An attack and the Attack action are different things. The Attack action is one specific action that lets you make an attack, but attacks can also be produced by spells, Bonus Actions, Reactions, and other features. True Strike is a spell that uses your Action and, as part of that spell, tells you to make one weapon attack.

At level 7, a hit with True Strike can therefore include the weapon's damage, your spellcasting ability modifier, True Strike's 1d6 additional Radiant damage, and Divine Strike's additional 1d8. If True Strike came from Magic Initiate and Wisdom was chosen as the feat's spellcasting ability, that attack can use Wisdom.

The larger damage sequence should not be described as three or four weapon attacks, though. Spirit Guardians deals damage through a saving throw, not an attack. Spiritual Weapon makes a separate spell attack. Under the base 2024 rules, both Spirit Guardians and Spiritual Weapon require Concentration, so they normally cannot operate together. If a War Domain feature specifically removes Concentration from Spiritual Weapon, that specific exception needs to be checked against the subclass's exact wording.

Rule the individual interactions first. Whether the resulting build feels too strong is a separate balance question.

Yes. In SRD 5.2.1, Quickened Spell can change Sunbeam’s casting time from an Action to a Bonus Action. After Sunbeam is active, the spell says you can use a Magic action to create a new line of radiance, so the Sorcerer can use that action on the same turn to produce a second beam.

Treat them as two separate 6d8 lines, not one 12d8 beam. Each line affects the creatures in its area and calls for its own Constitution saving throw; a failed save also causes the Blinded condition until the start of your next turn.

Quickened Spell restricts casting another level 1+ spell that turn, but Sunbeam’s later Magic action is using an effect of the already-cast spell, not casting Sunbeam again. The spell also requires Concentration, so protecting Concentration matters if you want additional beams on later turns.

The combination is strongest when battlefield geometry lets both lines catch useful targets; against scattered enemies, the first-turn action compression may be less valuable.

Rules reference: D&D 5e SRD 5.2.1 — Quickened Spell and Sunbeam.

Under the 2024 rules, not automatically. A wizard can add a level 1 or higher wizard spell to a spellbook when the wizard finds that spell and can prepare spells of that level, paying the normal transcription time and cost. The warlock's Pact of the Tome, however, creates a Book of Shadows containing supernatural magic that only that warlock can access; the chosen spells function as warlock spells for that character.

That wording does not clearly establish the Book of Shadows as an ordinary written source another character can read and transcribe. Cantrips are also outside the wizard's spellbook-copying rule, which only covers spells of level 1 or higher.

If a DM wants cross-copying to work, treat it as an explicit table ruling rather than as an automatic entitlement. A clean version is to allow transcription only when the spell is also a wizard spell of level 1 or higher, then use the wizard's normal copying costs and time. That preserves the wizard's spellbook procedure without turning every Pact of the Tome choice into a freely transferable spell source.

Earlier 5e printings use different Pact of the Tome wording, so check the exact rules version being played before applying this ruling.

Not by Blink alone. Under the current 5e spell, you disappear into the Ethereal Plane at the end of your turn on a successful Blink roll and return at the start of your next turn. That timing does not give you a normal turn in the Ethereal Plane in which to spend movement walking through a wall or floor.

Your return point is also constrained. You reappear in an unoccupied space you choose that you can see within 10 feet of the space you left. Blink lets you perceive the plane you departed while you are Ethereal, but it does not say that opaque objects become transparent. A space hidden behind an ordinary solid wall therefore is not a valid return point merely because you are temporarily on another plane.

If some separate effect actually lets you see an otherwise hidden space, the visibility requirement could be satisfied, subject to the other limits of the spell. Likewise, an effect that grants movement at the relevant time could create a different interaction.

The key distinction is that Blink is a brief defensive displacement with a tightly specified return. It is not a short-duration version of Etherealness that gives you an interval to explore or move through material barriers.

Based on the two 2014-era texts quoted, Eldritch Smite and Mace of Dispater can both apply to the same qualifying hit because each has its own trigger and each spends its own spell slot; neither quoted effect says that using one prevents the other. Eldritch Smite still keeps its once-per-turn limit.

Divine Smite needs to be separated by rules version. In the 2024 rules, Divine Smite is a level 1 spell cast as a Bonus Action immediately after a qualifying hit. The 2024 rules also limit you to spending one spell slot to cast a spell during a turn. That does not by itself prohibit spending slots on non-spell features, but it does matter when mixing legacy material.

The important limitation is source compatibility. Mace of Dispater is Unearthed Arcana, and the quoted Eldritch Smite is from a 2014 supplement; neither interaction is established by the 2024 core reference alone. So the safe ruling is: the quoted Mace and Eldritch Smite stack if your DM allows those texts together, but a triple stack with 2024 Divine Smite should be confirmed against the exact legacy-content policy and wording your table uses.

Yes. A melee spell attack can qualify for the rule that lets an attacker knock a creature unconscious, so Steel Wind Strike can be used nonlethally when one of its attacks would produce the required result.

The important rules term is melee attack. The knockout rule does not require a melee weapon attack, martial training, or a particular damage type. Steel Wind Strike instructs the caster to make melee spell attacks, so force damage does not disqualify it and being a Wizard rather than a martial class does not change the interaction.

Under the 2024 rules, when a melee attack would reduce a creature to 0 Hit Points, the attacker can instead leave it at 1 Hit Point with the Unconscious condition. The older 2014 rules handle the resulting unconscious creature differently, but they likewise allow a melee spell attack to be used for a knockout.

A DM can decide to change that rule for a particular campaign, but that would be a house rule rather than a limitation inherent to Steel Wind Strike. If the concern is fictional plausibility, describe the successful attack accordingly: the magical strike overwhelms the target without delivering the final lethal force. The mechanics already establish that the attacker can make that choice; the description can follow the ruling rather than inventing an additional precision requirement.

Suggestion can influence what a seasick creature does, but it does not make the creature physiologically immune to seasickness. The spell causes a creature that fails its save to pursue an achievable course of activity to the best of its ability. It does not say that it removes bodily symptoms, conditions, penalties, or other ongoing effects.

That distinction matters if the DM has given seasickness mechanical consequences. A suggestion such as continuing to work despite feeling ill could affect the sailor's behavior, provided the requested activity meets the spell's requirements. The sailor might stop complaining, remain at a station, or attempt normal duties. Any independently established effect of the sickness still applies unless some other rule removes it.

If seasickness exists only as description and has no mechanical effect, there is more room for presentation. The enchanted sailor might insist that everything is fine while visibly pale and unsteady, creating a useful distinction between compelled conduct and unchanged physical reality.

I would preserve that boundary rather than letting clever wording turn Suggestion into a general-purpose cure. Doing so keeps the spell flexible without allowing it to duplicate effects that actually change a creature's physical state. If the table wants magical treatment for seasickness, establish a remedy that explicitly addresses the sickness instead.

Barkskin is an AC floor, not a bonus that is automatically added on top of another Armor Class effect. Its current rules text says that the target has AC 17 if its AC would otherwise be lower than 17. If the character's applicable AC is already 17 or higher, Barkskin does nothing to increase it further.

For an interaction with Bladesinging, first determine the character's AC using the exact Bladesinging feature and every other applicable rule. Then compare that result with 17. If the result is below 17, Barkskin makes it 17. If the result is 17 or more, Barkskin does not turn that into 17 plus another modifier.

There is one source limitation here: Bladesinging itself is not contained in the available rules reference, so its precise feature wording cannot be verified from that rules text. If the feature grants a bonus to AC, apply that bonus according to its own wording before checking whether Barkskin's floor matters. If a different version of the feature instead establishes another AC calculation, that exact text must be used.

The general adjudication is therefore straightforward: calculate the AC produced by the applicable rules, then use Barkskin only when that AC would be below 17. Do not treat the spell's 17 as a new base number unless another rule explicitly says to do so.

The 2024 version changes what Counterspell does, but it does not appear to contain a blanket rule that prevents one Counterspell from being answered by another Counterspell. If the normal trigger and other casting requirements are satisfied, a chain can still occur.

What changed is the spell's resolution. Rather than the older automatic-versus-check structure, the new version makes stopping the spell depend on the target's saving throw. That can make the reaction feel less decisive: the caster spends a limited resource and reaction, but the opponent may simply succeed on the save.

At the table, keep the information consistent. Players should know what their characters can perceive before deciding whether to spend Counterspell, and identical situations should use the same standard for identifying a spell or recognizing its apparent importance.

If several creatures can Counterspell in the same moment, resolve each reaction in order and move on. Do not turn the exchange into a separate negotiation about whether each participant would have anticipated every later reaction.

The practical issue is less whether counterspell wars are impossible and more whether the revised spell produces the kind of interruption play the group enjoys. That is a pacing and resource question after the RAW interaction has been established.

I would still resolve the attack's damage; Armor of Agathys dropping the attacker to 0 Hit Points should not retroactively erase an attack that has already hit.

There is an important source limitation here: Armor of Agathys itself is not included in the available SRD 5.2.1, so its exact current spell wording and timing cannot be established from that rules document alone. I would therefore not present the following as verified SRD RAW.

For adjudication, separate the events. The attack roll has already succeeded. That successful hit is what creates the situation in which the spell's retaliatory effect matters. If the cold damage then reduces the attacker to 0 Hit Points, nothing inherently rewinds the successful attack or cancels consequences that were already being resolved.

This also produces the cleaner fiction. The ghoul lands its claw while supernatural cold races back through its body. It can collapse from the retaliation while the blow it already landed still injures the warlock. Treating its death as though the claw suddenly never connected requires an additional cancellation rule rather than following naturally from the established hit.

If the exact timing matters at your table, check the version of Armor of Agathys your campaign is actually using and follow any explicit trigger language there. Without such language, resolving both consequences is the least disruptive ruling.

The current 5e rules do not establish a universal tactical decision window based on whether the table physically rolls the saving throws or the damage dice first. For an effect that makes multiple creatures save against the same damage, the rules say to roll that damage once for all targets; each target’s save then determines whether it takes the full amount, half, or whatever the effect specifies.

Lightning Bolt follows that pattern: creatures in the line make Dexterity saving throws and take 8d6 lightning damage on a failure or half on a success. Nothing in that spell creates a separate permission to wait for one set of dice before deciding to use another feature.

If a class feature, magic item, or other ability can modify the damage, its own trigger controls when the choice is made. Wording such as “when you roll damage,” “when a creature fails a saving throw,” or “after you see the roll” is important; the table’s convenient rolling order does not rewrite that trigger.

For smooth play, pick a consistent procedure—often saves first, one shared damage roll second—and resolve any triggered features at the moment their text specifies. That prevents incidental dice order from becoming an unintended tactical resource.

Telekinesis does not explicitly say that it breaks whatever attaches an object to a structure. The current spell lets you move a Huge or smaller object, automatically if nobody is wearing or carrying it, but it does not provide a separate rule for destroying hinges, chains, masonry, rails, or other fixtures.

That makes “move the gate” and “tear the gate free” two different questions. If the target is already a discrete movable object—an unbarred door, loose slab, cart, or detached portcullis—the spell’s object movement is straightforward. If the supposed object is still physically integrated into a wall, the rules do not say that the spell automatically overcomes every attachment merely because another spell happens to include a “not fixed to a surface” restriction.

The DM therefore has to identify what the target actually is and what prevents movement. A bar or latch might be manipulated with the spell’s precise control. A gate embedded in a stone structure may require its fixtures to be broken, opened, or otherwise dealt with first.

That ruling also preserves a useful distinction in play: Telekinesis can apply extraordinary controlled force without silently becoming a universal demolition effect whose object-size limit overrides all construction.

If the character is a Druid/Thief Rogue using a spell scroll, Fast Hands does not change the spellcasting ability. Under the 2024 rules, Fast Hands can let a Thief use a Bonus Action to take the Magic action to use a magic item that normally requires an action. The spell scroll then applies its own rules.

A spell scroll is readable only if the spell is on your spell list. If it is on the Druid spell list, the Druid’s spellcasting ability is Wisdom. If the scroll contains a spell of a level you can normally cast, there is no special ability check just for reading it. If the spell is higher level than you can normally cast, the scroll requires an ability check using your spellcasting ability, with a DC of 10 plus the spell’s level.

So for a Druid/Thief with no other spellcasting feature, that check uses Wisdom. Rogue does not turn it into an Intelligence check merely because Fast Hands supplied the action timing.

The important distinction is that Fast Hands answers “when can I use the item?” The spell scroll answers “can I cast this spell, and what ability applies?” Those are separate rules.