Skip to content

Visual Novel Creator

Author story data in Roblox Studio, then install a runtime that players use in-game.

Visual Novel Creator helps when a Roblox visual novel has outgrown loose scripts and scattered assets. You still build in Roblox Studio, but the story itself becomes structured project data: chapters, scenes, nodes, variables, characters, assets, and runtime settings.

That structure matters because the editor can inspect it. It can show warnings before play, draw scene flow in the Story Map, preview authoring changes quickly, compile runtime data, and install a player-facing runtime into your game.

Install the plugin Read beta limitations Coming from SVNE?

The plugin and runtime are separate pieces.

The plugin is the authoring surface. You use it inside Studio to create and preview the story. The runtime is installed into your place when you want players to start, save, load, choose options, submit text, and move through the story in a real play session.

Preview and runtime testing answer different questions. Preview helps you move quickly while writing a scene. Play testing checks the installed runtime, saves, settings, text filtering, and world interaction nodes.

You do not need to write story code to start. Use nodes and Properties first. Reach for runtime extensions only when a project needs custom runtime button behavior that the built-in fields cannot express.

VNC is currently in beta. Before building a large route, read the beta limitations and node status pages so you know which features need extra runtime testing.

Branching stories

Build dialogue-heavy scenes with typewriter text, speakers, choices, variables, conditions, and clean branch flow.

Visual novel presentation

Use backgrounds, sprites, portraits, audio, title cards, effects, and sprite slots without hand-wiring runtime code.

Runtime UI

Ship menus, save/load, autosave, settings, logs, chapter select, return-to-menu flows, and player-facing presentation.

Safe customization

Start with Properties fields and presets, then use runtime extensions only when a project needs custom behavior.

Beta-aware workflow

Check limitations, node maturity, runtime testing, and exact defaults before depending on a feature at scale.

  1. Install the plugin.
  2. Create or load a VNC project.
  3. Author chapters, scenes, nodes, assets, variables, characters, and runtime settings.
  4. Preview story paths while you work.
  5. Compile and install the runtime into the place.
  6. Start a Studio play session and test the player-facing flow.