What Even Is a Visual Novel?

 

Having decided to make a visual novel, I needed to actually understand what one is. Everyone has a rough idea of what a dating sim is, but if you ask "so what is it exactly?" the answer gets surprisingly vague.

Dating simulation? Visual novel? Text adventure? Choice-based game? It's hard to tell whether these terms all point to the same thing or different things. If you're going to build something, you need to know exactly what you're building. So I asked AI.

Let's Start with Terminology

"What's the difference between a dating sim and a visual novel?"

That was the first question I threw at Claude. Here's the summary.

Visual Novel is a format. You read text, see background images and character illustrations, and encounter choices along the way. A game centered on the act of reading. There are plenty of visual novels that have nothing to do with romance — mystery, horror, sci-fi, slice of life. The content can be anything.

Dating Sim (Bishoujo/Otome) is a theme. A game where romance with characters is the core objective. Many use the visual novel format, but not all. Games where you raise stats and schedule dates also fall under this umbrella.

Dating Simulation is close to the English equivalent, but strictly refers to games with simulation elements — stat management, scheduling.

Interactive Fiction is the broadest category. Any form where the reader intervenes in the story. Text adventures, visual novels, choice-based novels, even tabletop RPGs.

The hierarchy looks like this:

Interactive Fiction (broadest)
  └── Visual Novel (format)
        └── Dating Sim (theme: romance)
  └── Text Adventure (format)
  └── Choice-based Novel (format)

What I'm building is a dating sim in visual novel format. A game you read, watch, and choose through. Romance at the center, but not simple romance — a game that digs deep into the emotions of relationships.

The Structure of a Visual Novel

With the genre understood, I needed to look at the structure. I asked AI: "What are the technical components of a visual novel?"

Breaking down the response, a visual novel consists of four layers:

1. Text Layer — The body of the game. Dialogue, narration, internal monologue. Where the player spends most of their time. The equivalent of a novel's prose or a film's dialogue and narration.

2. Visual Layer — Background images, character sprites, CGs (event illustrations). This is where the "visual" in visual novel comes from. It supplements atmosphere and emotion that text alone can't fully convey.

3. Choice Layer — Branch points. The player's only means of intervening in the story. Selecting a choice changes the story's path. This layer is what separates visual novels from novels and films.

4. System Layer — Save/load, backlog, auto mode, settings. Infrastructure supporting the player experience. Convenience features that make it a game.

From a creator's perspective, layers 1 and 3 are what matter most. What story to tell, and where to let the player choose. The rest is already provided by engines like Ren'Py.

What Makes It Different from Other Games?

Here's where a question arose. If a visual novel's structure is this simple, can you even call it a game?

Action games have controls. Puzzle games have problems to solve. RPGs have combat and progression. Visual novels have... reading and choosing. That's it.

I put this question to AI: "Is a visual novel really a game?"

The answer was interesting. The key point:

If you define games by "complexity of input," a visual novel isn't a game. But if you define games by "meaningful choices," a visual novel is the purest form of game there is.

In most games, player choices are tactical. Use this item or not, go left or right, attack or defend. There's a right answer, or at least an optimal one.

Choices in visual novels are different. Many have no right answer. "Say it now, or later?" "Be honest, or let it go?" "Move closer, or keep distance?" These choices have no optimal solution. The answer changes with the situation, the relationship, and the player's own values.

That's why choices in visual novels feel less like tactical decisions and more like emotional judgments. The player projects their own values into the game. That's an experience other genres struggle to deliver.

Common Routes and Individual Routes

Visual novel story structures follow several patterns. Here's what AI and I mapped out:

Linear — No branches, a straight line. Essentially a novel. Called a kinetic novel.

Branching — Splits at certain points. Different choices lead to different stories. The most basic visual novel structure.

Common Route + Individual Routes — Everyone experiences the same early story, then branches off by character in the mid-game. The most common structure in dating sims.

True Ending — A final route that only unlocks after clearing all individual routes. Fragmentary truths from each route converge at the end.

Loop — The player repeats the same time period, making slightly different choices each cycle. The repetition itself becomes part of the narrative.

Among these, I was most interested in the common route + individual route structure. But not the simple "branch by character" approach — I wanted a structure where the same story is experienced with different emotions. That's something I'll dig into in later entries.

AI's Map of the Genre Landscape

What was interesting was how the visual novel genre's position became increasingly clear through conversation with AI.

Visual novels sit at the intersection of games and literature. They combine the interactivity of games with the narrative depth of literature. In exchange, they're weak as games in terms of feel, and lighter than novels in text density. A medium that takes the strengths of both sides while inheriting both sides' weaknesses.

But there's a point where those weaknesses become strengths. Novels don't let readers intervene. Films don't let audiences intervene. Games let you intervene, but mostly through physical input. Visual novels demand emotional intervention. They make you actually choose: "What would I do in this situation?"

Why this structure touches human emotion — or fails to — is the question this project will explore.

What You Need to Know Before Building

Through conversation with AI, my understanding of the genre crystallized. To make a visual novel, you ultimately need three things:

Story. Text worth the player's time to read. Characters, situations, conflict, resolution. Not so different from writing a novel.

Choice Design. Where to give the player agency. How those choices alter the story. This element doesn't exist in novels.

Emotion Design. What feelings the story and choices should make the player experience. This is the hardest and most important part.

Code? That follows after these three are settled. Ren'Py handles most of the technical side.

But here's one thing I noticed. When I asked AI "what is a visual novel?", it organized structure and classification beautifully. Genre history, technical composition, comparison with other media. Information synthesis was excellent.

But when it came to "why do people get hooked on this genre?", the answers stayed surface-level. "Because emotional immersion is possible." "Because choices create meaning." Not wrong, but the real answer wasn't in there.

I think that's less about AI's limitations and more about the nature of the question. "Why do humans feel real emotions from fictional relationships?" isn't a question you can answer with information. It requires memory and experience.

So in the next entry, instead of asking AI, I'm going to reach into my own memories. The games I used to play. What I felt playing them. Whether those emotions still hold up.

---

Next: The Games I Used to Play — Memories Surfaced by Thinking About Visual Novels