goldtag

Scenes Push Emotions Forward — The Context System We designed the emotion system. With the three-layer model, we separated character disposition, momentary emotions, and relationship state. We also established a structure where love is never increased directly but emerges from a combination of conditions. Yet as the conversation with AI continued, one missing piece became visible. Tracking emotions alone is only half the picture. "Are you okay?" Consider this single line. Hearing it on a rainy night, in front of someone's house, just the two of you — concern, protectiveness, and intimacy rise. Hearing it in a school hallway during lunch, surrounded by friends — it is nothing more than a casual check-in. Hearing it on a cold evening right after a fight — it is an attempt at reconciliation, tinged with regret. The line is the same. The emotions are different. What creates the difference is the scene . Scene Context The structure AI proposed is this: separate from emo...

A Design Where Love Is Never Directly Increased In the previous part, we designed the three-layer emotion model. Among its principles, one stands above the rest. The variable called love does not exist in the system. There is no love += 1. Instead, love "emerges" from a combination of other variables. This is the core of this system and the biggest difference from conventional affection-meter systems. Why Love Should Never Be a Direct Variable When I discussed this topic with AI, it offered an interesting perspective. "Love is not on the same level as other emotions." Sadness, anger, jealousy, fear. These are momentary emotions. They rise or fall in response to specific events. But love is different. Love is closer to the result of accumulated relationship interpretation than a momentary emotion. Trust is high. Dependency exists. Intimacy has built up. There is a touch of jealousy. Fear of loss is present. The player repeatedly chooses the other person as a ...

Translating Emotion into Variables — The Three-Layer Emotion Model Now it's time to design emotion in earnest. Having identified the limits of Affection+1, we need to build a system to replace it. I told AI: "I don't want a single affection variable. I want a variable system that represents human emotion more realistically." And this is where AI really started showing its strength. Structuring emotion — decomposing something abstract into variables and layers — is exactly the kind of work AI excels at. How Many Emotions Do We Need? That was the first question. "How many emotion variables should we have?" AI's answer was surprisingly cautious. "More isn't always better. Too many variables leads to overengineering." Then it proposed a crucial distinction: The types of emotion you express can be many. But the state values the system directly tracks must be structurally organized. What does that mean? Love, sadness, anger, arrogance, env...

Is This a Limitation of Games, or of Design? So far, we've analyzed why visual novel emotions are special and how they differ from other media. We've confirmed that the visual novel genre has a structure well-suited for handling emotion. But most real-world visual novels don't use that potential fully. Many provide an experience closer to "walkthrough optimization" than genuine emotion. Why? AI and I dug into the structural problems of existing visual novels. The World of Affection+1 Most visual novels work like this: Choose option A, the character's affection rises by 1. Choose option B, affection stays the same or drops. Cross a threshold and you enter the romance route. Fall short and you get a bad or normal ending. This system is easy to implement. One variable, a few conditionals. Testing is simple. Balancing is intuitive. Low production cost means most visual novels adopt this structure. But this structure has fundamental problems. When I asked AI...

Why Can't Other Games Draw Out Emotion? We've analyzed why emotion emerges in visual novels. The reverse question follows naturally: why can't other games do the same? Of course, "can't" is an overstatement. People have cried playing The Last of Us, felt their chest tighten in Final Fantasy. But those emotions mostly come from cutscenes or story events. It's rare for the gameplay itself to produce relationship emotions. Why? AI and I dug deep into this topic. Games' Basic Structure Clashes with Emotion Most games are built on a challenge-reward structure. Defeat enemies for experience, complete quests for rewards, clear stages to progress. The emotions this produces are achievement, tension, thrill. Intense, but different in texture from relationship emotions. Relationship emotions sit at the opposite end of efficiency. Liking someone is inefficient. Anxious, irrational, uncontrollable. The challenge-reward structure fundamentally conflicts with ...

Drawing Out Emotion in a Short Time In the previous entry, I said emotion is built by time. But there's a contradiction. A visual novel can't be infinitely long. Player time is finite. You need to generate real emotion from a character relationship within a few hours — a dozen at most. Films make people cry in two hours. Short stories leave lasting impressions in under ten thousand words. How do they do it? And what's the same and different about visual novels? The Concept of Emotional Density Discussing this topic with AI, one concept crystallized: Emotional Density. Emotional density is the concentration of emotional change a player experiences per unit of time. The same thirty minutes can feel entirely different depending on whether nothing happens or a decisive relationship moment unfolds. High density isn't always better. Sustained intensity creates fatigue. Sustained low density creates boredom. What matters is controlling the density — the rhythm. AI drew ...