You’re sitting at the table, your Druid-Cleric multiclass is staring down a hoard of ghouls, and you think you’ve found the ultimate "I win" button. You cast Moonbeam, then you slap Sanctuary on yourself. In your head, you’re an untouchable beacon of lunar death. But then the DM clears their throat, reaches for the Player’s Handbook, and the vibe shifts.
Honestly, the question of does moonbeam break sanctuary is one of the most persistent headaches in Dungeons & Dragons 5e. It's the kind of thing that starts friendly debates and ends with someone digging through Jeremy Crawford’s Twitter archives from 2015.
The short answer? It depends on when you do it and how your DM reads the word "affects."
The Raw Mechanics: Why It's So Confusing
To understand why this is such a mess, we have to look at the exact wording of Sanctuary. The spell says it ends if you make an attack, cast a spell that affects an enemy, or deal damage to another creature.
Now, look at Moonbeam. It’s a concentration spell. When you first cast it, you’re clearly casting a spell. If you drop that beam right on top of a goblin, you are "casting a spell that affects an enemy." Sanctuary is gone. Boom. Done.
But what if the beam is already there?
This is where players try to get cheeky. If you cast Moonbeam on Turn 1, then cast Sanctuary on Turn 2, you aren't "casting a spell" anymore—you're just maintaining one. And since Moonbeam doesn't require an attack roll, you aren't "making an attack" in the technical sense of the D&D rules.
Does Moonbeam Break Sanctuary if You Move It?
This is the billion-dollar question. Once Sanctuary is up, you can use your action to move that silvery pillar of light 60 feet. If you slide that beam onto a boss, does the protection drop?
✨ Don't miss: Finding Secret Seashell Locations in Link's Awakening Without Losing Your Mind
Basically, if you go by the strict Rules as Written (RAW), there is a loophole. Moving an existing spell effect isn't the same as casting a new one. This is the "Moonbeam Cheese" that Baldur's Gate 3 players fell in love with. In the video game version, you can move that beam around like a deadly vacuum cleaner while staying perfectly safe under Sanctuary.
However, tabletop D&D is a bit more prickly. The 2018 errata added a tiny, devastating clause to Sanctuary: it ends if the warded creature deals damage to another creature.
If that beam hits someone and they take 2d10 radiant damage, you are the one who dealt that damage via the spell. The moment the numbers subtract from the enemy's HP, your Sanctuary evaporates. You can't hide behind a silver mirror while simultaneously melting someone's face with moonlight. It’s just not how the magic is supposed to flow.
The "Hazard" Argument
Some folks argue that Moonbeam is a "hazard," like a pit trap. They say the spell doesn't deal damage; the area deals damage when a creature starts its turn there.
💡 You might also like: Madden 25 Draft Questions: How to Ace the Combine and Secure a Top Pick
It's a clever argument. Kinda legalistic. But most experienced DMs will see right through it. If you’re the one holding the concentration and you’re the one moving the beam, you are the source of the harm.
Jeremy Crawford and the "Design Intent"
If you look at official rulings (Sage Advice), the lead designer Jeremy Crawford has been somewhat consistent here. The intent of Sanctuary is to protect someone who is staying out of the fray.
- RAI (Rules as Intended): Any aggressive action that results in an enemy getting hurt should break the spell.
- RAW (Rules as Written): There used to be a gap where "ongoing damage" from a previous turn didn't count, but that gap was largely closed by the "deals damage" wording in newer printings of the book.
If you’re playing with an older version of the Player's Handbook (pre-2018), you might actually be able to get away with this. But in 2026, most digital tools like D&D Beyond use the updated text.
What About the 2024 Rules Update?
If you've made the jump to the new 2024 Player's Handbook, the "Sanctuary Cheese" is officially dead and buried. The new wording is even more explicit. It ends if you "deal damage" or "force a creature to make a saving throw."
Since Moonbeam forces a Constitution saving throw the moment a creature enters it or starts its turn there, Sanctuary will snap the second the spell does its job. No more loopholes. No more "I'm not touching them, the moon is!" excuses.
Real-World Table Strategy
So, if the combo is mostly broken, how do you actually use these spells together?
You use Sanctuary for its actual purpose: protecting the healer. If you’re a Druid/Cleric and your job is to keep the fighter from dying, Sanctuary is amazing. You can still use your actions to Help, use Dash, or cast non-offensive buffs like Bless or Cure Wounds (since they don't affect an "enemy").
If you really want to use Moonbeam effectively, forget about Sanctuary. Instead, look at ways to keep enemies inside the beam.
- Thorn Whip: Pull them back into the light.
- Grappling: Have the Barbarian hold them in the fire.
- Plant Growth: Make it impossible for them to walk out of the radius.
Actionable Next Steps for Players
If you’re planning to bring this to your next session, don't surprise your DM with it mid-combat. That’s a recipe for a 30-minute rulebook session that kills the momentum.
- Check your PHB printing: Look at the Sanctuary text. If it says "deals damage to another creature," your Moonbeam plan won't work for more than one tick of damage.
- Talk to your DM about "Ongoing Effects": Ask them, "If I have an active spell like Moonbeam or Spike Growth and then I cast Sanctuary, does the protection break the next time someone accidentally walks into my spikes?"
- Pivot to "Support Sanctuary": Use the spell when you need to stabilize the party, not as a way to become an invincible tank.
The "Moonbeam/Sanctuary" combo is a classic example of "too good to be true." While the mechanics of 5e can be crunchy and sometimes leave doors open for exploitation, the spirit of the game usually wins out. You're either a protector or a destroyer; trying to be both at the same time usually just results in a broken spell and a very grumpy DM.