Narrative & Dialogue Prompts

Main quest structure with built-in subversion at Act 3. The two Act 5 endings give writers an A/B framework to develop in parallel.

Side quests with genuine dilemmas are remembered; fetch quests are not. The three-option structure ensures no "right answer" exists at design time.

Mystery quests need clue redundancy and red herrings planned before writing begins. This template prevents the "one missing clue blocks progress" bug.

Companion quests need a clear before-and-after character change or they feel pointless. The "dialogue changes permanently" section forces that commitment.

Daily quest systems need variety enforcement or players see the same quest twice in a row and stop engaging. This designs the anti-repetition logic from the start.

Mystery quests need exactly the right amount of information — enough to solve with thought, not so much that it's obvious or so little it's guesswork. This structure hits that balance.

Escort quests are universally disliked because NPCs are helpless and routes are boring. This forces design decisions that fix both.

Faction choice quests fail when one option is obviously right. This forces both sides to have legitimate arguments and genuine costs.

Timed quests that end in game-over frustrate rather than engage. Partial failure with real consequences makes time pressure feel meaningful without being punitive.

Reputation systems feel empty without visible world-state changes at each tier. This design ties reputation to tangible NPC behavior from the start.

Heist quests without a planning phase are just "go to location, get thing." The intelligence-changes-execution loop creates genuine player investment before the climax.

Revenge quests that end with NPC gratitude regardless of approach ignore moral consequence. Designing divergent NPC reactions based on method creates genuine ethical weight.

Survival quests with "save everyone" possible outcomes lose tension. Designing guaranteed partial loss — with player choice determining who is lost — creates the moral weight that makes these scenarios memorable.

Political quests fail when player choices don't accumulate. This chain forces relationship tracking to matter by making the final quest's options depend entirely on prior choices.

Fetch quests fail because items are identical, locations are generic, and the reason for collection is vague. One item with a mini-story and one non-combat acquisition make the quest feel curated.

Emergent quests discovered through observation rather than quest-givers are the design achievement that players discuss for years. The "world event without player" requirement makes the world feel genuinely alive.

Faction quest chains that are just task lists miss the narrative purpose of faction membership. The ethically gray quest 4 and the revelation in quest 5 are the beats that make players feel like they actually joined something real.

Environmental puzzles without deliberate clue visual language become frustration rather than discovery. The "wrong answer feedback without saying wrong" requirement is the UX craft that makes environmental puzzles fair.

Morally ambiguous quests that withhold information from the player feel unfair. The complication must be discoverable mid-quest so players genuinely grapple with new information rather than making a choice in the dark.

Branching dialogue with disposition tracking and branch convergence. The convergence requirement ensures no path blocks the player from story progress.

Interrogation scenes are most effective when the suspect's tells are consistent across approaches. This lets attentive players feel smart for noticing patterns.

Relationship-state dialogue is the payoff for player investment in NPC bonds. The identical-content requirement prevents relationship tracking from feeling cosmetic.

Alien communication styles that the player must decode create memorable puzzle-dialogue moments. The "three failed attempts" structure teaches the mechanic organically.

Villain monologues fail when they're pure exposition. This forces a moment of genuine player reflection — the "they have a point" beat is what players quote for years.

Skill-check dialogue becomes pointless when all paths yield the same outcome. This forces genuine branching based on how the player built their character.

Dialogue options that label emotions ("I'm sorry" vs "It's not my fault") feel artificial. Behavioral options that the player fills with meaning feel real.

Trade dialogue is usually a single persuasion check. This three-beat structure makes negotiation feel like a micro-story with real dramatic tension.

Interrogation scenes that always yield the truth reward no skill. Designing partial information and reading-the-suspect as a mechanic makes dialogue a puzzle.

Companion disagreements that end in automatic forgiveness feel hollow. This design forces the companion to have a position they may or may not abandon.

First villain meetings that reveal villainy too early remove dramatic irony. The "interesting or correct" requirement creates the uncanny respect that makes great antagonists.

Romance dialogue that names the emotion ("I think I love you") is almost always cringe. Behavior-driven revelation with maintained ambiguity creates the romantic tension that players replay.

Farewell scenes that end on "goodbye" waste their emotional potential. The "thing left unsaid" is where farewell scenes live — this prompt forces the writer to identify it before writing a word.

Impaired NPC scenes done well extract information through subtext rather than blunt confession. The morning-after dialogue is what separates a scene with consequence from a throwaway moment.

Post-battle scenes are emotional windows that most games leave empty. The "truth said only in this window" requirement creates the character-revealing moments players remember.

Exposition delivered as questions-and-answers breaks character voice. This exercise forces organic information delivery — the design note teaches the technique, not just the result.

Reputation systems that only change NPC tone miss the narrative opportunity: the information revealed at HONORED tier should recontextualize something the player thought they understood. The gate has to mean something.

Companion banter without a cooldown system causes the same exchange to fire three times in a dungeon. Designing the trigger priority and cooldown before content production prevents the "are you sure?" line becoming a meme.

In-world tutorial text that maintains immersion while being functionally clear. The "why" requirement ensures players are motivated to try the mechanic, not just told to.

Loading tips that players actually read. The "make experienced players surprised" requirement ensures tips go beyond basics — the test of whether a tip set is any good.

Onboarding sequences that teach through story events retain players far better than popup tutorials. The "done something cool by minute 3" rule is the retention benchmark.

Three-tier tooltip depth teaches casuals without boring veterans. The "never say simply" rule alone improves tooltip quality dramatically.

Tutorial-through-narrative is significantly better than explicit instruction, but hard to write without a template. These three personality types cover most game archetypes.

Accessibility explanations that are condescending or buried in "accessibility" menus reduce uptake. Neutral practical language across all player types removes stigma and improves adoption.

Advanced technique discovery text creates the "did you know you can do that?" moments that players share online. The NPC hint that precedes discovery is what makes finding it feel earned.

Returning player friction is the biggest gap in most game UX. Players who don't remember where they were or what to do next churn again immediately. This bridges the gap.

Death messages seen repeatedly become the most hated text in the game if they're tone-deaf. Variation by cause and performance context prevents the message from becoming associated with frustration.

Companion arcs without mapped stages collapse in the middle of development. Stage 5's forced binary choice prevents the "nothing bad ever happens" companion arc.

Story outlines that force hero/antagonist mirroring produce the thematic depth that separates memorable games from forgettable ones.

The three-act breakdown with emotional arc keeps story structure aligned with game pacing. The "darkest moment tied to flaw" requirement prevents hollow climaxes.

Tragic endings feel like bad design unless the flaw was clearly the player's ally before it became their downfall. This arc forces that setup.

Side character arcs that run parallel without intersecting main story feel disconnected. Three deliberate intersection points give them gravity without stealing focus.

Found family arcs fail when the fracture is external — the group is only tested by the world, not by each other. Internal tension in the split is what makes the reunion feel earned.

Unreliable narrator structures that plant clues before the mid-game reveal create the retroactive reread experience — players replay not for content but for understanding.

Time loop narratives without a thematic question ("what does repeating the same moment until you get it right say about grief / regret / control?") are escape room puzzles. This forces the theme before the mechanics.

The ghost-flaw-want-need structure is the most reliable framework for character arcs that feel emotionally inevitable rather than contrived. Pre-filling it before writing any dialogue prevents the character from being inconsistent.

Multiple endings gated behind a final "pick your ending" menu feel like surveys. Divergence rooted in mid-game choices makes players feel their playstyle earned their ending rather than selected it.

Opening cinematics set the game's promise. The "introduce protagonist indirectly first" rule creates instant intrigue without a clunky "here's the hero" moment.

Boss dialogue that acknowledges the player's journey makes the confrontation feel earned. The "acknowledgment of journey" requirement prevents generic villain speeches.

Ending design that treats all outcomes as valid prevents players from feeling cheated by non-"true" endings. Each ending answering different questions is the key.

Twist scenes need pre-planted seeds or they feel arbitrary. This prompt forces you to design retroactive foreshadowing before writing the rest of the game.

Forced deaths need justification to feel earned rather than cheap. The "why player choice is removed" rationale forces narrative designers to defend that decision.

Opening cinematics that info-dump lose players before the game starts. The "no exposition monologue" rule alone dramatically improves opening engagement.

Reunion scenes that go immediately to happiness miss the dramatic tension of what changed during separation. The "awkward before warm" rule captures that reality.

Villain reveals fail when they're exposition dumps. The recontextualization requirement — making old info feel new — is what elevates a reveal to a twist.

Villain defeat scenes with generic "you'll never stop me" final lines waste the culmination of the entire story arc. The recontextualizing final line is the punctuation mark the whole game was building to.

Mid-game twists revealed through exposition rather than revelation fail the "show don't tell" test at the most important narrative moment. The retroactive clue requirement proves the twist was planned.

Betrayal cutscenes that give allies unmotivated villainy produce disbelief. Writing the betrayal so the ally's logic is understandable — even sympathetic — is the difference between a twist that lands and one that alienates.