11 · Emotionally Adaptive Storytelling | Generative AI for Game Development

[0:00]Generative AI for game development, emotionally adaptive storytelling. Learn how games remember feelings and how to build characters that change with you. Hello, this is Liam in for Bear. It's easy to think characters just need better dialogue. They don't. They need memory and the decency to change. Six terms then we're off. Emotional memory, past feelings shaping present reactions. System level design, emotion that persists across scenes. Character class, one object holding a character's emotional state. Emotional decay, feelings fading naturally over time. Prompt adaptation, feeding emotional state into AI prompts. Tonal whiplash, emotional shifts too abrupt to believe. Most games adapt to what you do. Emotionally adaptive stories adapt to

[0:42]How you do it, your tone, your trust, your regret. The goal isn't realism, it's resonance. A kind word in a tense moment, a quiet gesture of protection, small things that echo. They decide who stands with you in crisis. Disco Elysium turns even your own psyche into a system of conflicting emotional voices. Life is Strange 2 grows a brother, not a meter, and Mass Effect earns squad loyalty across a trilogy. Hundreds of small moments shape Daniel's personality, and by the end you see yourself reflected in who he became. Two architectures, scene level branching where each scene decides alone and system level design where emotional state persists and shapes every scene

[1:21]After it. This isn't the illusion of choice. It's an authentic emotional journey and the deepest question isn't what you'll do, it's who you'll become. The engine starts by encapsulating one character class per character, trust, anger, memory, mood, even personal decay rates. No more scattered dictionaries. Scenes become data, the reunion, the final mission, each a card holding choices with trust changes and tones attached. Swap scenes without rewriting the engine. Feelings decay, ignore I/O for five scenes and his anger quietly drains. And above the characters, global dials turn, world state, moral trajectory, the shape of everything. And it really runs. The chapter's own character class executed live. An

[2:04]Apology raises trust, an accusation spikes anger. Five silent turns let it fade, and every change is remembered. Then prompt adaptation, trust, anger, and the last two memories flow into the language model's prompt. So, every generated line arrives already grounded in your shared history. The full loop, the player chooses, sentiment analysis reads the tone, emotions update, a new prompt is generated, and the narrative steps into its next scene. Beware tonal whiplash. A character who forgives betrayal in one line feels hollow. Emotional change must be gradual, believable, earned. That's what decay and pacing are for. Anchor the system in authorial intent. Guardrails and thresholds no emotional data may cross. Test with real players

[2:48]And punctuate, adapt at the moments that matter, not everywhere. And remember, emotion is a tool, not the story. The system should amplify the game's core message, never overshadow it. The failure mode has a name, manipulation. A game that farms your guilt for purchases has crossed the line. Players should always know when their emotions are being read. Design for safety, content warnings, opt-outs, off-ramps for heavy moments. And think long-term, build systems that leave players more resilient, not smaller. Done thoughtfully, these systems turn games into living conversations, shared journeys between designer and player, unique every time, remembered long after. Let's recap with Claude. Emotionally adaptive stories ask who you'll become,

[3:30]Not just what you'll do. System-level design beats scene-level branching. Feelings persist and compound. A character class, scene data, decay, and prompt adaptation turn a demo into an engine. Balance means gradual change, authorial guardrails, and emotions serving the story. Reading emotion carries ethical weight, consent, safety, and no manipulation. Done well, games become living conversations between designer and player. Your turn, paste this into Claude. Help me design an emotional state container for one NPC in my game. I will describe the NPC. You propose three emotional variables with starting values, one decay rule, and one guardrail the emotion system may never cross. Then simulate three player actions, one

[4:13]Kind, one cruel, one silent, and show [snorts] me the state after each. Then check two things yourself. Does your decay rule name what fades and how fast? And does the guardrail protect a story beat, not just a number? If the guardrail only caps a meter, it isn't guarding anything. Emotionally adaptive storytelling at Nick Bear Brown.