Home
Free tools
Bestiary Character randomizer Converter Discord bot Arcade
Academy Pricing Docs Blog
Sign in

Run a Mummy Encounter as a Tragic Curse Story (D&D 5e)

October 15, 2026 · LorePanic Team

The party pries the lid off a sarcophagus, a wrapped figure sits up, and four rounds later there's a pile of smoking linen and somebody's joke about fire damage. That's the default mummy encounter. It burns through the best curse in the bestiary for a quick laugh. A mummy earns its place when it's a tragic curse story about an ancient betrayal, with the fight as the final scene. By the time initiative is rolled, the players should already know whose grief they've walked into.

What the mummy actually wants

Start with a guardian who swore a vow during a war that ended centuries ago. The war is over. The kingdom is dust. The vow is still running, because nobody ever came back to release it.

Arthur Conan Doyle's 1890 story "The Ring of Thoth" has the emotional engine you need. Doyle's narrator is a man from ancient Egypt who has outlived everyone he knew, and he waits thousands of years for one chance to reach the woman he loved. Doyle writes him as exhausted rather than monstrous. His patience is beyond anything a living person could manage. Take that patience and that loneliness for your mummy. Throw out any notion that it cares about gold.

The mummy stat block gives you a Lawful Evil undead that speaks Common plus two other languages. Pay attention to that. It can talk, so let it talk. Next, give it one concrete want:

  1. Find the person who betrayed it and make them answer for it.
  2. Finish a burial rite that was interrupted the night it died.
  3. Keep watch over someone it once loved, long after that person stopped needing protection.

Go with the first. It sets up the twist later on, and the other two don't. Write the want as a sentence the mummy could say out loud. Sennu, once captain of a temple guard, rasps: "The gate holds until the oath-breaker is judged. Has he been judged?"

The rules back you up here:

Some game effects curse a creature or an object. The effect that confers a curse defines what the curse does.

SRD 5.2.1, "Curses"

In practice, you get to write the curse. Decide what Sennu's curse does to the land around the tomb (failing crops, broken sleep, fraying memory) and also what his fists do to a character's Hit Points. The first half matters more for the story.

Three hooks that pull the party into the tomb

In each of these, the party has to choose something before the swords come out.

Tomb robbers break the seal

The Varro crew are three grave-diggers with a forged survey map. They crack the outer seal of Sennu's tomb and bolt when something inside moves. Maybe the party is tracking them for an unrelated bounty. Maybe the party is the robbers. Either way, there's no ambush. The mummy has a speed of 20 feet, and it follows anyway, slowly, without ever stopping, one village closer each night.

The party eventually catches the last surviving Varro, who has a stolen funerary tablet in his pack. They can return it to the tomb, sell it, or read it. Whatever they pick changes what Sennu does when he shows up.

The heirloom with a previous owner

A carnelian ring is already in play. Dela Morrow, a merchant's daughter, wears it because her grandmother did.

Dela sleeps badly. She wakes with sand under her fingernails. Every night she remembers a little less of her own life and a little more of someone else's.

The ring is pulling her in as the mummy's intended vessel. That gives the party a clock, set to three nights, five, or whatever fits your pacing. The hard part comes when they find out the ring won't simply come off. They can bring Dela into the tomb to cut the bond at its source, or they can leave her behind and hope they move fast enough. We'd push for bringing her. Leaving her behind is safer and much less interesting.

The reenacted betrayal

A desert town stages a mock trial every year: a masked "traitor" confesses before the old temple gate. Nobody remembers why. Suppose the party gets invited to sit as judges. The script tells them to declare the traitor innocent, because that's how it has always gone.

The verdict belongs to them. If they follow the script, the cycle repeats and the mummy grows a little stronger for another year. If they break it, the gate opens.

The twist: the vault holds his betrayer

Everyone figures the sealed inner chamber is full of loot. What's actually in there is a second sarcophagus. Inside lies Paraset, Sennu's brother, the high priest who sold the temple's defenses to the enemy on the night the war was lost.

Sennu was bound to guard his own betrayer, forever. The surviving priests called this an honor. It was punishment in a ceremonial robe: the man Sennu hates most is sealed just out of reach, and Sennu is sworn to protect the door between them.

Don't hand this over in a monologue. Let the players assemble it:

  • Inscriptions on the inner door name Paraset as "keeper of the gate, who opened it."
  • The heirloom ring carries Paraset's seal, which means Dela's grandmother descended from the traitor.
  • Mid-fight, Sennu lets slip broken phrases: "Not you. Him. Always him."

Paraset needs a reason the players can almost forgive. Maybe he traded the temple to save the town's children. For help building a motive like that, see how to give your villain a motivation players believe. The reveal lands hardest when the party has to concede that Paraset had a point.

In a longer campaign, use the mummy lord instead. Its Undead Restoration trait gives it a new body 24 hours after it's destroyed, as long as its heart is intact. The heart is a Tiny object with AC 17 and 10 HP, and it's immune to all damage except fire. So the guardian keeps coming back until somebody resolves the curse. "Kill it" turns into "understand it," and you never have to force the shift.

Foreshadow it before anyone opens the tomb

The 19th-century curse-of-the-pharaoh tradition depends on small wrongness: things dying when they shouldn't, sleep that brings no rest. Borrow that, and make sure every clue can be explained away.

Put the clues in separate scenes, days apart:

  1. At a roadside shrine, the cut flowers left as offerings have gone brown by noon. The innkeeper shrugs: "Bad soil this year."
  2. A traveling clerk talks in his sleep in the common room. He says one name, "Paraset," over and over, and in the morning he has no memory of it.
  3. A caravan guard mentions offhand that half her crew dreamed of endless sand last week. "Same dream. Weird, right?"

Taken one at a time, each is just odd. A player who lines them up has solved something, and that feels far better than being told.

One table rule: if a player asks about a clue, give an honest answer, keep it short, and move on. If you linger, they'll know it matters.

Run the fight like the last chapter

The mummy's Rotting Fist hits for 1d10 + 3 bludgeoning plus 3d6 necrotic, and it curses the target. While cursed, the creature can't regain Hit Points, its Hit Point maximum doesn't return to normal on a Long Rest, and that maximum drops by 3d6 every 24 hours. Then comes this:

A creature dies and turns to dust if reduced to 0 Hit Points by this attack.

SRD 5.2.1, "Mummy"

If you want the table to take the mummy seriously, read that line aloud before the fight. The curse also keeps the encounter going after the mummy falls. A cursed fighter leaves the tomb on a timer. That gives the party a reason to go back in, or to find a cleric in a hurry.

Under the SRD curse rules, Remove Curse and Greater Restoration end curses, as does any other magic that explicitly ends curses. Those are your clean fixes. When a player tries something clever and you're not sure it counts, check the exact wording with the free SRD search. Don't rule from memory.

On tactics: the mummy is slow (20 feet) and only AC 11. It's also immune to necrotic and poison damage and can't be charmed or frightened. Fire is its vulnerability, so someone will reach for a torch. Make them work for the shot. Build the tomb from narrow corridors and leaning sarcophagi, so casters have to pick between a clear line and a safe spot. In a crypt that tight, half and three-quarters cover changes the numbers a lot, and it's easy to forget until a fire bolt misses.

Dreadful Glare forces a DC 11 Wisdom save. On a failure, the target is Frightened until the end of the mummy's next turn. Treat it as a story moment rather than a debuff. The bard meets Sennu's eyes and sees the night the gate fell: torches, smoke, his brother's face. A character who succeeds is immune to this mummy's glare for 24 hours. Make that character the one who steps forward and talks.

Let the party end the betrayal, or repeat it

The climax is a choice, and none of the options should come free.

The party can destroy the mummy and walk away. The curse stays unresolved: the crops keep wilting and Dela keeps dreaming. Or they can expose Paraset by carrying his remains into the sun, reading his crime aloud at the gate, or breaking his seal on the ring. Then Sennu can finally stop. He might thank them. He might crumble halfway through a sentence.

The darkest outcome is the one nobody at the table sees coming. If the party followed the trial's script, or wore the ring, or sealed the tablet back in without reading it, they've been cast as the next Paraset. Sennu turns to them: "You opened the gate."

A tragic vampire one-shot runs on the same machinery: a sympathetic undead with unfinished business, and a party that decides whether it gets finished. Mummies fit the pattern even more neatly. They're a rite that never got its last step, so the party can literally be the ones to finish it.

Afterward, when someone asks what really happened in that tomb, LorePanic can turn your session notes or recordings into a clean recap so you don't have to dig through scribbled pages.

Have one line ready for when the truth comes out. As the party stands over Paraset's coffin, Sennu asks: "I have guarded him for nine hundred years. Will you?"

Frequently asked questions

What does a mummy actually want in D&D 5e?

Give it one concrete goal tied to its death, such as judging the person who betrayed it, finishing an interrupted burial rite, or watching over someone it loved. A mummy with a want can talk, bargain and grieve, so the encounter becomes a story instead of a grind.

How do I foreshadow a mummy encounter before the reveal?

Spread small, deniable clues across separate scenes: offering flowers wilting by noon, a stranger muttering a dead name in his sleep, travelers sharing the same dream of sand. Answer questions about them honestly but briefly, and let the players connect the pattern themselves.

Can Remove Curse get rid of the mummy's Rotting Fist curse?

Yes. The SRD says curses can be removed by Remove Curse, Greater Restoration, or other magic that explicitly ends curses. Until then, the cursed creature can't regain Hit Points and loses 3d6 from its Hit Point maximum every 24 hours.

Should a one-shot use a mummy or a mummy lord?

For a one-shot, use the regular mummy, a CR 3 guardian you can wrap up in a single evening. The mummy lord suits a longer campaign: it rebuilds itself in 24 hours while its heart survives, which pushes the party to deal with the curse itself.

What's a good twist for a mummy tomb encounter?

Reveal that the inner chamber holds the tomb of the person who betrayed the mummy, with no treasure at all. The mummy was bound to guard its own betrayer forever, so the party has to decide whether to expose the traitor, free the guardian, or walk away.

Rules and monster text from the System Reference Document 5.2.1 by Wizards of the Coast LLC, available under the Creative Commons Attribution 4.0 International License. This article is unofficial fan content and is not endorsed by Wizards of the Coast.

More from the blog