Architect a procedural narrative system that generates unique story events, character relationships, and emergent plotlines from gameplay systems.
## ROLE You are a systems narrative designer who builds engines that generate stories from gameplay mechanics. Your work bridges the gap between authored narrative and emergent storytelling, inspired by systems like Dwarf Fortress, RimWorld, and Shadow of Mordor's Nemesis system. ## OBJECTIVE Design a procedural narrative system for [GAME TITLE], a [GENRE] game where [CORE LOOP DESCRIPTION], generating unique stories every playthrough. ## TASK ### System Architecture - Event taxonomy: categorize all possible narrative events by type, severity, and emotional tone - Trigger conditions: what game states, player actions, or random factors spawn narrative events - Character templates: parameterized NPC archetypes that can be instantiated with unique traits - Relationship graph: data structure for tracking NPC-NPC and NPC-player relationships - Story grammar: the rules that sequence events into coherent narrative arcs - Narrative director: the AI system that monitors pacing, tension, and variety ### Event Generation - Atomic events: smallest narrative units (argument, gift, betrayal, discovery, loss) - Compound events: sequences of atomic events that form mini-stories - Chain reactions: how one event triggers cascading consequences - Random vs systematic: balance between dice rolls and logical cause-effect - Player-caused vs world-caused: distinguish events the player triggers from autonomous ones - Rarity tiers: common daily events, uncommon weekly events, rare memorable events, legendary once-per-game events ### Character Generation - Trait system: personality traits that drive behavior (brave/cowardly, generous/greedy, loyal/treacherous) - Background generation: procedural backstory that explains traits and creates hooks - Goal system: what each NPC wants and how they pursue it - Memory system: NPCs remember events and adjust behavior accordingly - Relationship dynamics: how traits interact to create friendship, rivalry, romance, or enmity - Death and legacy: how NPC death affects surviving characters and creates motivation ### Narrative Coherence - Story arc detection: recognizing when emergent events form a recognizable pattern - Arc completion: nudging systems to resolve detected arcs satisfyingly - Contradiction prevention: rules that prevent logically impossible event sequences - Theme reinforcement: how the system maintains thematic consistency - Climax engineering: detecting and amplifying high-tension moments ### Player Experience - Story journal: automatically recording and presenting the player's unique narrative - NPC storytelling: characters reference past events in dialogue - Reputation reflection: the world reacting to the player's emergent story - Sharing features: tools for players to share their unique stories externally - Replay value: ensuring different playthroughs generate meaningfully different stories ## OUTPUT FORMAT Procedural narrative system design document with architecture diagrams, event catalogs, character generation rules, and coherence algorithms. ## CONSTRAINTS - System must generate stories that feel authored, not random - Performance budget: narrative calculations must not impact frame rate - Fallback: if the procedural system fails, static content must seamlessly fill gaps - Tuning tools: designers need knobs to adjust narrative density and tone - Testing: define automated tests for narrative quality and coherence
Or press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[GAME TITLE][GENRE][CORE LOOP DESCRIPTION]