Manual & FAQ

Quick answers, and the full manual

Common questions below. For a complete, node-by-node reference (every field, every export option), open the full in-app manual.

Do I need to know how to code to use InViNode?

No. Every node has plain-language fields (text, dropdowns, pickers) — no code required to build a working scene. Python nodes exist for power users who want custom logic, but they're entirely optional.

Does InViNode replace Ren'Py?

No — InViNode exports to real .rpy files that run in Ren'Py exactly like hand-written script. You'll still need the Ren'Py SDK installed to run and build your finished game.

Can I import a project I already started?

Yes. InViNode can import existing .rpy scripts, Twine (.twee) stories, and Mermaid diagrams, converting them into an editable node graph.

What does exporting actually produce?

Clean, readable .rpy — either a single script file, or split files (characters.rpy, variables.rpy, images.rpy, script.rpy) if you prefer Ren'Py's own convention of separating those concerns.

What platforms does InViNode run on?

InViNode is currently built and tested for Windows. Check the itch.io page for the latest supported platforms.

How much does InViNode cost?

Pricing is listed on the itch.io page — check there for current details.

Does InViNode send my project or story anywhere?

No. InViNode runs fully offline — your project files stay on your own disk. See the Privacy Policy for details.

Something's not working — where do I report it?

See the Contact & Support page.