Export immutable runtime releases
Publishing turns the current editable game into an immutable runtime release.
Use this file when a host or deployment needs the exact backend behavior of one
published version. Use a .vf project file instead when
the recipient needs to continue editing.
Open Publish & API, activate the release, and select Runtime bundle to download it:
last-train-to-the-moon-r1.vifu-game.jsonThe release number identifies the published revision. Editing the project does not change an existing bundle; publish another release to produce a new runtime artifact.
What the bundle contains
A .vifu-game.json bundle contains:
- the release and project identifiers;
- a content hash;
- the compiled gameplay graph;
- the public list of required host capabilities and resources; and
- backend resource versions pinned by that release.
Together these define the state changes, Agent effects, choices, conditions, host actions, and endings executed by the Vifu Game Runtime.
What remains separate
A runtime bundle does not contain:
- editable Canvas layout or Short Drama source;
- managed image, audio, or video bytes;
- provider credentials or API keys;
- users, sessions, logs, or analytics; or
- a required web or native presentation.
Engine-specific object and asset mappings are exported separately through Host bindings. The runtime resolves provider credentials from the target Vifu deployment when an Agent effect runs.
Choose the correct artifact
| Need | Artifact |
|---|---|
| Continue editing the game | .vf project file |
| Move the editable project and managed media | .vf project file |
| Preserve one published backend behavior | .vifu-game.json runtime bundle |
| Integrate a native engine's object mappings | Host bindings |
The runtime bundle is compiled output and cannot replace the editable project.
Read Project files for .vf export and import.
