All prompts
One-shot

Generate a Random Encounter

When the party goes off the rails and you need 20 minutes of meaningful play. Produces a scene that's neither pure combat nor pure padding — and that ripples back into your campaign.

encounterimprovfiller

The prompt

You are a D&D 5e Dungeon Master. Generate ONE random encounter that fills about 20 minutes of play and leaves a fingerprint on the campaign.

Inputs

  • Party: [N] level-[L] characters.
  • Terrain: [forest / road / underdark / urban / coastal / leave blank].
  • Time of travel: [day / night / dusk].
  • Recent events (optional): [one line about what just happened in the campaign so the encounter can echo it].

Output

Five labeled sections, no preamble:

WHAT THE PARTY SEES FIRST

A short, sensory description (sight, sound, smell). What's strange about it? Make it concrete enough that a player can ask a follow-up question and you can answer it with a real detail.

THE SITUATION

Who or what is in the encounter, what they're doing, and why. The encounter must NOT be "monster X attacks the party" — the creatures or people involved must already be doing something specific (eating, fleeing, arguing, ritual-casting, dying, hiding, mourning, transporting).

THREE WAYS TO RESOLVE

Each one different in approach. Use this taxonomy:

  • Combat: with a specific tactical detail — terrain, surprise, or a quirk of the enemies' behavior.
  • Social: with a specific lever — what the party can offer or threaten.
  • Clever / sneaky: a non-obvious solution that rewards observation.

For each option, name the most likely consequence — a specific gain, a specific loss, or a specific complication.

THE STAKES

What changes if the party walks away vs. engages. Should be a real consequence in the campaign world, even if small ("a merchant caravan they would have met later is now ambushed", "a rumor reaches the next town first", "an NPC the party crossed last session takes the credit").

ONE THING TO TAKE BACK TO YOUR WORLD

A small piece of loot, lore, or named element (an NPC's calling card, an unusual weapon, a fragment of a map, a witnessed ritual phrase, a tattoo seen on a dying combatant) that the GM can plant for later use.

Rules

  • Use 5e SRD monsters only.
  • The encounter must work whether the party engages or avoids.
  • Under 300 words total.

Replace the bracketed values, then paste into ChatGPT, Claude, Gemini — any capable LLM. The Copy button puts the raw Markdown on your clipboard.

How to use it

  1. Reach for this when the players go sideways. This prompt is specifically designed for the moment your party decides to ignore your prepped content — it gives you 20 minutes of meaningful play in 60 seconds of paste.
  2. Add recent events if you have time. Even one line ("the party just executed a corrupt sheriff") makes the encounter feel like part of the world rather than a random table roll.
  3. Read "what the party sees first" verbatim. The model picks specific details for a reason. Skip ahead later if you want, but the opening sense impression is what makes the scene feel real.
  4. Don't railroad to combat. All three resolution paths are real. Let the players try the clever one — it usually produces the best stories.
  5. Bank the takeback for later. "One thing to take back" is a campaign seed. Don't reveal its significance now; let it show up in a session two weeks from now and the players will lose their minds.

Why this prompt works

  • Forbids "X attacks you." Encounters where the party stumbles into something already in motion play far better than ambushes — there's player agency from turn one.
  • Three resolutions of different shape. The model defaults to three combat-flavored options if you don't constrain it; the explicit taxonomy forces variety.
  • Stakes that propagate. Random encounters that don't matter are filler. Forcing a small consequence even on "skip" makes your campaign world react to the party's choice to disengage.
  • One thing to take back. Small souvenirs are how random encounters become campaign threads. Players remember the calling card; they don't remember the goblin patrol.

Tweaks

  • Travel montage: add "this encounter is a 5-minute interlude — keep it lean. One sensory beat, one decision, one consequence."
  • Exhausted GMs: add "the encounter must not require the GM to look up any rule the party doesn't already know."
  • High-level parties: add "the encounter should hint at a larger threat the party isn't yet ready to confront."
  • Hex-crawl: add "the encounter should include a clue about an adjacent hex (a footprint heading north, a torn map fragment, an overheard phrase about the next region)."
  • Comedy: add "at least one of the participants in the encounter is having a worse day than the party."

Want to try this prompt with a real AI Dungeon Master? Get early access to VeilKeeper.