Use a test place
Early story work is easier when you can freely install, update, and delete runtime objects without risking a production place.
Visual Novel Creator starts as a Studio plugin because authoring is different from gameplay. You need a place to write, organize, preview, check, and compile story data before players ever touch it.
The plugin is that place. It is where you create projects and edit Properties. The installed runtime is what players use later.
Because VNC is in beta, start by reading Beta Limitations if you plan to use saves, text input, world nodes, or extensions early.
Use a test place
Early story work is easier when you can freely install, update, and delete runtime objects without risking a production place.
Save before runtime changes
The plugin can install runtime objects into your place. Save first so you can roll back if you are experimenting.
Keep Studio open
VNC is meant to be used from inside Studio, alongside the Explorer, Output, and Play testing tools you already use.
Once the editor is open, start with one of the project actions:
The project source data stays separate from the installed runtime bundle. That lets you keep authoring data in the place while reinstalling runtime scripts and assets as the story changes.
Do not start by designing every menu, save slot, and sprite slot. Start with one scene. Add one dialog node, preview it, then add one choice. Once that loop feels clear, the rest of the editor will make more sense.
The Editor Tour is the quickest next stop if you want to understand each panel and menu before writing more.
Your first payoff is simple: you can see story text on screen without committing to the final runtime setup yet.