25 · Project Variations | Generative AI for Game Development
The final chapter video shows that the narrative engine from earlier chapters is not game-only. Changing the goal config, vocabulary and pacing turns it into a tutor, a marketing tool or a journaling assistant.
The last video in the series asks whether an engine built for games can do anything else. Its answer is that it does whatever the goal config says: educate, persuade, comfort or entertain. This chapter introduces no new projects. Instead it offers new purposes for the system the reader already built, a modular engine made of JSON scenes, GPT expansions, decision logic, emotional scoring and procedural chains. It accompanies the book by Shesh Narayan Gupta and is narrated by Liam for Humanitarians AI.
Six terms for customizing a workflow
The video defines six terms. A workflow is the pipeline from input to story. Domain vocabulary is the set of words a field needs. The outcome is what the story is meant to do: learn, persuade, comfort or entertain. Personalization means fitting stories to the person. Collaborative intelligence treats AI as a partner rather than a replacement. Ethical design means building in reflection at every step.
Education
The Flask and JSON engine can become a language tutor, with vocabulary hidden inside plot choices. It can also become a history simulation in which the learner's decisions fork the timeline.
Marketing
Examples include a skin care quiz that makes the user the hero of a self-care journey, emails that evolve with the recipient's replies, and loyalty paths that reward engagement. The video describes this as broadcast becoming dialogue, and it warns that the personalization line must hold.
Wellness
A therapeutic journaling assistant uses the same engine with slower pacing, affirming logic and gentle words tuned to comfort.
Customize the inputs, not the engine
Customization means changing the inputs, the vocabulary and the outcome while the engine stays. A teen slang chatbot and a corporate simulator share nothing but architecture. The video shows a sketch, honestly labeled as such, in which one traveler at a crossroads is educated, persuaded and comforted by changing only the goal config. The recommended method is to define the goal first, whether that is to calm, excite, educate, provoke or heal. Then iterate by testing against user reactions, observed behavior and ethical review, because no config is final.
Three directions forward
The video closes with three directions: greater personalization, collaborative intelligence and ethical design. Its framing is that generative storytelling is not just technology but a craft shaped by human intent, and that the pen now belongs to the reader.
Key takeaways
- One modular engine can serve many domains.
- Education, marketing and wellness are three adaptations of the same Flask and JSON engine.
- Change the goal config, vocabulary and pacing, not the engine.
- Define the goal first, then iterate against real user reactions.
- Marketing personalization turns broadcast into dialogue but must be handled carefully.
- No configuration is final; test it against behavior and ethical review.
- An ethical line should be specific to the domain, not a platitude.
Try it yourself
Paste the video's prompt into Claude and name one non-game domain. Ask for a goal config covering the outcome, ten domain vocabulary words, the input format and the pacing, then one scene running under it, one ethical line you must not cross and a way to test the adaptation. Check that the ten words are ones a practitioner would recognize, and that your ethical line is specific to this domain. If it could apply to anything, it protects nothing.
Full transcript(auto-generated, with timestamps)
[0:00]Generative AI for game development, project variations, one engine, countless purposes, the series finale on adapting your narrative systems. Hello, this is Liam in for Bear. My engine only does games. No, it does whatever the goal config says, educate, persuade, comfort. The engine stays, the purpose changes. Six terms, then we're off. Workflow, the pipeline from input to story. Domain vocabulary, the words each field needs. Outcome, learn, persuade, comfort, entertain. Personalization, stories fit to the person. Collaborative intelligence, AI as partner, not replacement. Ethical design, reflection at every step. One modular engine, JSON scenes, GPT expansions, decision logic, emotional scoring, procedural chains. This final chapter isn't new projects, it's new
[0:47]Purposes for the system you already built. Education, the Flask and JSON engine becomes a language tutor, vocabulary hidden in plot choices, or a history simulation where your decisions fork the timeline. Marketing, a skin care quiz that makes you the hero of your self-care journey, emails that evolve with your replies, loyalty paths that reward engagement. Broadcast becomes dialogue, and the personalization line must hold. Wellness, the therapeutic journaling assistant, same engine, slower pacing, affirming logic, gentle words tuned to comfort. Customization means changing the inputs, the vocabulary, the outcome, learn, persuade, comfort, entertain, while the engine stays. A teen slang chatbot and a corporate simulator share nothing but architecture. A thesis
[1:33]Executed, one traveler at a crossroads educated, persuaded, comforted by changing only the goal config. A sketch honestly labeled. Define the goal first, calm, excite, educate, provoke, heal. Then iterate, test against user reactions, observed behavior, ethical review. No config is final. Three directions, greater personalization, collaborative intelligence, ethical design. Generative storytelling isn't technology, it's a craft shaped by human intent. Now, the pen is yours. Let's recap with Claude. One modular engine, JSON, decisions, emotion generation serves every domain. Education, tutors and simulations from the same flask and JSON you built. Marketing, quizzes and emails, broadcast becomes dialogue carefully. Wellness, the same engine slowed and warmed, tuned to comfort. Customize the
[2:23]Goal config, not the engine, then iterate against real reactions. Personalization, collaboration, ethics, and now the pen is yours. Your turn. Paste this into Claude. Help me adapt my narrative engine to one non-game domain. I will name the domain. You write the goal config, the outcome learn, persuade, comfort, or entertain, the domain vocabulary 10 words, the input format, and the pacing. Then show me one scene running under that config. Name one ethical line I must not cross and tell me how I'd test whether the adaptation works. Then check two things yourself. Is your vocabulary really the domain's 10 words a practitioner would recognize? And is your ethical line specific to this
[3:02]Domain, not a platitude? If it could apply to anything, it protects nothing. Project variations at Nick Bear Brown.
More from Generative AI for Game Development — Shesh Narayan Gupta
3:2724 · Templates and Frameworks | Generative AI for Game Development
3:1023 · Step-by-Step Projects | Generative AI for Game Development
3:1422 · Interviews with Industry Professionals | Generative AI for Game Development
3:1421 · The Future of Generative AI in Storytelling | Generative AI for Game Development
3:4620 · Best Practices for AI Storytelling | Generative AI for Game Development
3:30