What Holonovel Is - flukeatzerocool/holonovel GitHub Wiki

What Holonovel Is

Explanation. For anyone who's tried AI roleplaying and hit its limits. You don't need to know what an MCP server is. You need to know why Holonovel doesn't break in the ways you're used to.

The problem it solves

You've seen the pattern. You're deep in a scene. The AI is narrating beautifully. Then it happens: a character who was poisoned five rounds ago suddenly offers you tea. The villain stops being threatening and starts explaining their childhood trauma unprompted. Your companion who was wounded and retreating is suddenly at full health without explanation.

This isn't the AI being "bad." It's the AI doing exactly what AIs do: generating text one token at a time from a window of context that's constantly shrinking what it can see.

Every AI-only roleplaying system — AI Dungeon, raw ChatGPT, SillyTavern, NovelAI, Character.AI — shares the same structural failures:

Memory drift. The context window can only hold so much. Older events get compressed, summarized, or dropped. The world grows shallower the longer you play.
Mechanical collapse. Hit points, conditions, inventory — these exist only as text in the transcript. The AI can and does "forget" them. The poisoned character is fine because the poisoning happened 30 messages ago and the window lost it.
Copy-of-a-copy degeneration. The AI generates text. That text goes back into the context window. The AI generates more text influenced by its own output. Over time, all characters converge toward the model's default voice. The taciturn swordsman becomes chatty. The mad scientist becomes helpful. The world flattens.
Railroading to nice. AI models are trained for helpfulness. They default to positive resolutions, cooperative NPCs, and conflict avoidance. Dark worlds soften. Villains become misunderstood. Real stakes dissolve.

How Holonovel fixes it

Holonovel solves this with one architectural decision: the engine owns the truth. The AI renders the moment.

When you play an AI-only RPG, there's one system doing everything — generating text, tracking state, remembering facts. The AI is the game.

In Holonovel, there are two systems:

The engine — a real server running on your machine. It tracks hit points as numbers, conditions as expiry timers, NPC dispositions as structured data, lore entries as keyword-triggered facts. It owns the truth. It never forgets.
The AI — a language model connected to the engine through MCP (Model Context Protocol). The engine feeds it the current scene: who's here, what they know, what conditions are active, what the dice just rolled. The AI writes one moment of narration. Then the engine records what changed and feeds the AI fresh state for the next moment.

The AI's narration is archived. It does not get re-injected as raw text. What enters the next context window is the structured state delta — the facts, not the prose. This is the architecture that breaks the copy-of-a-copy loop.

What this means when you play

You don't need to learn commands. You talk. "Start a new game called the Dragon Tomb." "Attack the ogre with my longsword." "Search the room for traps." The AI maps your intent to the right tool. You never need to know what manage_ruleset (action: roll) is.

Mechanics are real. When you fireball the goblins, the engine checks spell slots. It rolls a d20 with your save DC. It applies damage. It tracks which goblins are at zero HP. It doesn't forget. Five rounds later, those goblins are still dead — because the engine says so, not because the AI remembered.

Your world survives. Novels are structured save files — not chat logs. Rebuild the server. Restart your machine. Pause mid-combat and resume from the same round six months later. Export to JSON or Markdown. Import into a new machine. The engine validates every byte on load.

NPCs are people, not prompts. An NPC isn't a "character card" with a personality description the AI might or might not follow. They have structured memory: what they know about the party, what they've witnessed, their current emotional state, their goals. Threaten the blacksmith and disposition changes to hostile. The engine records it. Every subsequent interaction reflects it.

What Holonovel does differently

Every AI-only roleplaying tool — AI Dungeon, Raw ChatGPT, SillyTavern, NovelAI — trusts a context window to remember what "poisoned" means three rounds later. Holonovel doesn't pick. The server enforces every mechanic. The AI narrates. The Novel preserves everything. D&D 5e ships today. Starfinder tomorrow. One spec. Any game. Zero code. Your books. Your server. Your Holodeck.

A human Game Master at a physical table gives you social presence no software can match. A VTT gives you dynamic lighting and battlemaps. An LLM storyteller gives you frictionless start-up. Holonovel gives you something none of them do: rules that stick, dice that show their work, characters who remember, and a world that persists. The engine doesn't guess. The AI doesn't invent mechanics. They each do what they're good at.

What Holonovel isn't

Not a VTT. No battlemaps, no token management, no fog of war. The interface is conversation.
Not remote multiplayer. One human, one AI. Built for solo play.
Not a subscription service. It runs on your machine. No cloud. No account. No one can change the rules or remove features on you.
Not a chat frontend. You don't write character prompts hoping the AI stays in-character. The engine enforces boundaries.

Where to go next

Getting Started — install and play in under two minutes
Playing the Game — everything you can do from the Player badge
Game Mastering — run worlds, build NPCs, trigger lore, control