03VD Engine
A branching interactive-cinema game engine — visual editor plus Windows/Android players.
- field
- Game Engine
- year
- 2025
- role
- Goals / fault-finding / sign-off
background
I wanted branching interactive cinema — the audience's choices rewrite where the story goes, which needs a complete engine from editor to players on two platforms.
The problem with off-the-shelf tools is that the editor and the runtime are two separate logics: a connection the editor allows may not survive playback. With dozens of hours of footage and hundreds of nodes, one plot change has an invisible blast radius.
what I did
I only set goals, find faults and sign off; all the code is written by AI. I set the release cadence and the delivery bar, pushing from "it runs" to "it's usable".
Boundaries came first: the graph drawn in the editor is the graph the player executes, with no translation layer in between; project files must be plain text and diffable; the node type set is closed and new types go through review.
outcome
A visual editor, Windows and Android players, and a complete QA, delivery and archiving system.
evidence index
Everything claimed above is backed by material that can be checked. Listed here by name and status.
- Demo videopending recording
- Feature listEditor and both players
- Release logCadence and delivery bar