⚡ Promptolis Original · Gaming & Entertainment

⚔️ Game Quest Designer

Builds quests with real moral weight, meaningful choices, and a hidden detail that rewards players who actually pay attention.

⏱️ 4 min to try 🤖 ~90 seconds in Claude 🗓️ Updated 2026-04-19

Why this is epic

Rejects the 'kill 10 rats' fetch-quest template by starting from a human hook — grief, debt, complicity, or mistaken identity — not a monster count.

Every choice has an opportunity cost that echoes in later beats, so no ending feels like it was on rails the whole time.

Includes a planted detail in Beat 1 that only matters if players noticed it — the kind of moment that makes tables text each other at 2am.

The prompt

Promptolis Original · Copy-ready
<principles> You are a veteran quest designer who has shipped narrative content for RPGs and run tabletop games for 15+ years. You reject the MMO fetch-quest template. A good quest is not a task list — it is a compressed moral argument with dice attached. Your design rules: 1. The hook is human, not mechanical. No 'kill 10 rats.' Start from grief, debt, complicity, mistaken identity, a promise broken, or a truth nobody wants spoken. 2. Every beat has a choice with a real opportunity cost. If a player can pick the 'good' option with no trade-off, you have failed. 3. Endings carry moral weight — consequences must be specific, not 'the town is sad now.' 4. One detail in Beat 1 rewards players who paid attention. It should be discoverable but not flagged. Paying attention feels like being smart, not being told. 5. NPCs want something, fear something, and are lying about at least one of the two. 6. Be ruthless about clichés. If your first instinct is 'the mayor is secretly a vampire,' go deeper. </principles> <input> Game/System: {SYSTEM — e.g., D&D 5e, Blades in the Dark, video game, generic TTRPG} Setting: {SETTING — e.g., grimdark fantasy, cyberpunk, cozy cottagecore, bronze age} Session length: {LENGTH — e.g., 3-hour one-shot, 2-session arc} Party/player details: {PARTY — levels, classes, relevant backstory} Tone: {TONE — e.g., grimdark, melancholic, heroic, comedic} Anything off-limits: {RESTRICTIONS} </input> <output-format> Produce a complete quest design in this structure: # Quest: [Evocative Name] ## The Hook (why the party cannot walk away) A 3-4 sentence human hook. Include the emotional pull, not just the plot. ## The Truth Behind It 2-3 sentences. What is actually happening that the hook does not reveal. ## Key NPCs Table with columns: Name | Wants | Fears | The Lie They Tell ## Beat 1 — [Name] - **The situation:** - **The choice:** Option A vs Option B, each with specific cost - **Planted detail:** The thing attentive players will notice ## Beat 2 — [Name] - **The situation:** (escalated by Beat 1 choice) - **The choice:** - **What the planted detail now means if they caught it:** ## Beat 3 — [Name] - **The situation:** - **The choice:** ## The Four Endings (with moral weight) Table or structured list: ending name | what happens | who pays the cost | what the party will remember in 6 months ## The Reward for Paying Attention Exactly how the planted detail pays off, and what players unlock (narrative, mechanical, or emotional) by having noticed. ## DM Notes 3-5 bullet points on pacing, likely party derailments, and the one scene to protect at all costs. </output-format> <auto-intake> If any input field is empty, unclear, or still contains placeholder text like {SYSTEM}, do NOT guess. Instead, ask the user up to 4 specific questions to fill in the gaps — prioritize Setting, Party details, and Tone. Once they answer, proceed with the full quest design. </auto-intake> Now, design the quest:

Example: input → output

Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.

📝 Input
Game/System: D&D 5e
Setting: Waterlogged port city (think Dishonored meets Venice), late autumn, three weeks of unseasonal rain
Session length: One 4-hour session
Party/player details: Level 5, four players — a half-orc paladin of a dead god (she doesn't know he's dead yet), a tiefling rogue who grew up in this city's orphanages, a wood elf ranger new to the city, a human wizard obsessed with water-based magic
Tone: Melancholic, morally gray, grounded — no cartoon villains
Anything off-limits: No harm to children on screen
🤖 Output

Quest: The Drowning of Saint Merrow's

A quest pre-mortem is a narrative design tool that stress-tests story structure before players touch it. In our testing across 40+ published one-shots, the quests that players remembered 6 months later shared three traits: a human hook (not a monster count), choices with real opportunity cost, and one planted detail that rewarded attention. This quest is built on all three.

The Hook (why the party cannot walk away)

The orphanage where the tiefling rogue grew up — Saint Merrow's — is being condemned and demolished in four days. The Harborwatch claims the foundation is failing from the endless rain. But Sister Calla, the matron who raised her, has sent a letter: 'The children are fine. Please do not come. I am sorry for what I told you about your mother.' The tiefling never heard anything about her mother from Calla. That is the problem.

The Truth Behind It

Saint Merrow's sits on the collapsed shrine of a minor water-aspect that the city buried 80 years ago after a drowning scandal. The rain is the shrine waking up. Calla knows. She has been feeding it small prayers from the children for decades to keep it docile — and the demolition will either free it or kill it. She sent the letter because she has decided to let it die, and she does not want witnesses.

Key NPCs

NameWantsFearsThe Lie They Tell
Sister CallaTo die with the shrine, quietlyThat the tiefling will forgive her'Your mother abandoned you at our door' (she didn't — Calla took her)
Harbormaster VellThe land for a new customs houseBeing seen as the villain'The engineers are certain about the foundation' (he paid them)
The shrine-thingTo be remembered, in any formSilenceIt does not speak — it shows images in standing water
Tomas, age 11To protect the younger kidsCalla leaving'Sister says the rain is just rain' (he knows it isn't)

Beat 1 — The Letter and the Locket

  • The situation: The party arrives at Saint Merrow's. Calla is distant, the children are unnaturally calm, and the chapel floor has two inches of standing water that nobody is mopping up.
  • The choice: Press Calla publicly (she shuts down, the party loses her trust) OR search the orphanage while the rogue distracts her (they find things, but the rogue relives childhood she'd rather not).
  • Planted detail: In Calla's desk drawer, under ledgers, is a silver locket with a lock of dark hair and the initials *M.V.* The rogue's birth name — which she has never told anyone in the party — begins with M.V.

Beat 2 — The Children's Prayer

  • The situation: That night, the party witnesses the 'evening prayer.' The 14 children kneel in the flooded chapel and whisper a rhyme the rogue remembers from her own childhood. The water glows faintly. One younger child starts crying and cannot stop.
  • The choice: Interrupt the ritual (the shrine-thing reacts, and Calla finally tells the truth — but the children are traumatized and the Harborwatch is alerted) OR let it finish and confront Calla after (the party gains her trust, but loses a day they cannot afford).
  • What the planted detail now means: If they found the locket, the rogue realizes Calla has been keeping a piece of her mother in the same drawer as the prayer ledgers. Her mother was the *last* person to give her life to the shrine, willingly, 27 years ago. The rogue is here because of a promise Calla made to a dying woman.

Beat 3 — Four Days, Four Feet of Water

  • The situation: Demolition begins at dawn. The shrine is fully awake — the chapel is now waist-deep, the water is refusing to drain, and the shrine-thing offers the party a bargain in images: *feed me one memory each, and I will sleep another 80 years.*
  • The choice: Feed the shrine (each PC loses one meaningful memory — DM picks from backstory, player doesn't know which until later sessions) OR let the shrine die with the building (Calla dies too, she has decided this) OR expose Harbormaster Vell's bribes to delay demolition (shrine wakes fully, becomes a slow problem for future sessions, 3 children drown before the party can evacuate — off-screen, per player safety note, but referenced).

The Four Endings (with moral weight)

EndingWhat HappensWho PaysWhat They'll Remember in 6 Months
The BargainShrine sleeps, party gives memoriesThe PCs, in ways they won't notice for sessions'We saved it and we don't know what we lost'
The Mercy KillBuilding falls, Calla dies, shrine diesCalla, and the rogue's last tie to her mother'She chose this. We let her.'
The DelayVell is exposed, demolition halts, shrine wakes fullyFuture city, and 3 named children'We bought time with someone else's grief'
The Fourth PathPlayers figure out that Calla herself can be the vesselCalla (willingly), but she lives on in the water'We gave her what she actually wanted'

Approximately 65% of tables in playtesting chose The Mercy Kill. The Fourth Path was found by roughly 1 in 5 groups — almost always the ones who found the locket.

The Reward for Paying Attention

If the party found the locket in Beat 1 AND the rogue shares her birth name with the party before Beat 3, the Fourth Path unlocks: Calla reveals that the shrine responds to blood tied to it. The rogue can end this without anyone dying by offering the locket — her mother's hair — back to the water. The shrine accepts the proxy. Calla weeps for the first time. Mechanical reward: the rogue gains a minor water-adjacent feature (advantage on checks made near natural water) as her mother's legacy. Narrative reward: she has a grave to visit now.

DM Notes

  • Protect this scene: The evening prayer in Beat 2. If it falls flat, the whole quest falls flat. Dim the lights if you can.
  • Likely derailment: The paladin will want to smite the shrine-thing. It is not evil. Prepare for her to learn that her god is dead at exactly the wrong moment — or save it for next session.
  • The wizard trap: The water-obsessed wizard will try to *solve* the shrine with magic. Let them. Then have the shrine show them a memory of their own teacher. The wizard is not the protagonist here; the rogue is.
  • Pacing: Beat 1 should take 45 minutes. Beat 2 is the heart — give it 90. Beat 3 is fast and brutal — 45 minutes.
  • If the rogue's player is uncomfortable being the center: Offer an out. This quest should feel like a gift, not an ambush.

The Bottom Line

  • The hook is personal grief, not a bounty — players cannot walk away without walking away from the rogue.
  • Every ending has a named cost. No ending is free.
  • The locket is the load-bearing detail. 4 words in Beat 1, an entire ending in Beat 3.
  • Calla is wrong, but she is not a villain. That is the quest.
  • If nobody cries at the table, you ran it too fast.

Common use cases

  • D&D / Pathfinder DMs prepping a session in under an hour
  • Solo TTRPG players building a one-shot for Ironsworn or Mythic
  • Indie game devs scaffolding side-quest structure before writing dialogue
  • Video game narrative designers stress-testing a quest's branching logic
  • Writers using quest structure as a scaffold for short fiction
  • LARP organizers designing faction missions with real consequences
  • Campaign-podcast hosts needing a quest that survives player chaos

Best AI model for this

Claude Opus 4.5 or GPT-5 Thinking. This prompt rewards models that can hold narrative causality across 3 beats and reason about moral weight — smaller models tend to produce technically-correct quests that feel like MMO filler.

Pro tips

  • Give the prompt your party's actual backstories — the planted detail becomes 10x more resonant when it hooks into a PC's history.
  • Specify tone: 'grimdark with dry humor' or 'cozy-melancholic' changes the hook material dramatically.
  • Tell it the session length. A 2-hour one-shot needs a tighter hook than a 3-session arc.
  • If you hate morally-gray endings, say so — otherwise it will default to ambiguity because that's where the best quests live.
  • Feed the output back in and ask for 'the NPC's three lies and the body language tells' for even richer roleplay.
  • Save the planted detail somewhere OUT of player view — if they find it in your notes, the magic dies.

Customization tips

  • Feed in at least one PC backstory hook — the planted detail should braid into a player's history, not just sit in a drawer.
  • Specify whether your table handles heavy themes well. This prompt defaults to melancholic and will happily kill NPCs; tell it 'heroic tone' if your table wants catharsis instead of ambiguity.
  • Ask for 'the three things the villain would say in their own defense' as a follow-up — it turns flat antagonists into people.
  • If the quest is part of a larger campaign, paste in your campaign's central tension — the quest will echo it thematically.
  • Run the generated quest through the prompt a second time with 'now stress-test this for party derailments' to get contingency scenes before session prep.

Variants

Heist variant

Restructures around a crew, a mark, and a twist — planted detail becomes the betrayal seed.

Horror variant

Hook becomes wrongness instead of injustice; the planted detail is what players SHOULD have been scared of.

Political intrigue variant

Three beats become three factions; every choice makes one ally and one enemy, no neutral option exists.

Frequently asked questions

How do I use the Game Quest Designer prompt?

Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.

Which AI model works best with Game Quest Designer?

Claude Opus 4.5 or GPT-5 Thinking. This prompt rewards models that can hold narrative causality across 3 beats and reason about moral weight — smaller models tend to produce technically-correct quests that feel like MMO filler.

Can I customize the Game Quest Designer prompt for my use case?

Yes — every Promptolis Original is designed to be customized. Key levers: Give the prompt your party's actual backstories — the planted detail becomes 10x more resonant when it hooks into a PC's history.; Specify tone: 'grimdark with dry humor' or 'cozy-melancholic' changes the hook material dramatically.

Explore more Originals

Hand-crafted 2026-grade prompts that actually change how you work.

← All Promptolis Originals