How does it compare?

There are plenty of ways to script a game’s story and logic in Unity, and plenty of ways to save. What Narramancer does differently is put the two together: saving is part of how graphs run, so a save made in the middle of a sequence picks up on the same step.

Tool	Scripting	Saving a sequence mid-way
Plain Unity	C# scripts, usually singletons and scripts that depend on each other to chain actions together.	You build it yourself: every script has to record where it is and restore it.
Unity Visual Scripting	Node graphs. Powerful and general-purpose.	Doesn’t record which node is running, so saving mid-sequence is something you build yourself, or forbid.
Fungus	Flowcharts, or Lua.	Doesn’t record which step is running, so the same applies.
Save-system assets	None. They save the data you hand them.	They don’t run your logic, so recording where each sequence was is still up to you. You can still use one alongside Narramancer for your own data.
Naninovel	Text scripts in its own scripting language, for visual novels.	Built in.
Narramancer	Node graphs, with a built-in table of nouns, adjectives and variables.	Built in. Every running graph is saved, including what it’s waiting on.

When to pick something else

If you’re making a visual novel and would rather write a text script than build node graphs, we recommend Naninovel. It’s a feature-rich engine with years of development and support behind it, and saving and loading are built in.

If your game has no sequences that run over time, and you only need to save some values, a dedicated save-system asset may be all you need.

When Narramancer fits

• Your game has story, dialogue, quests or behaviour that runs over time, and players should be able to save in the middle of it.
• You’d like that flow laid out in graphs you can see, rather than spread across scripts.
• You want a table of characters, items and places, with their properties, stats and relationships, saved for you.

See what gets saved, or get started.