Game SDK

↓ Download SDK 0.3.0

Internal VORIVOX development. Preview package: remaining gates are listed under compatibility.

Source ZIP and .vxgame package

Distinguish the source ZIP, installed game container and an individual session's launch manifest.

Source build

The internal developer prepares an ordinary ZIP with a clear entry point, local resources and media. Unity uses a Linux build; HTML5 uses browser assets compatible with a separately accepted Runtime Host. Exclude credentials, live manifests, node_modules and editor working directories.

Canonical package

A central administrator uploads the ZIP to a game version. Cloud validates the archive, determines runtime/entrypoint, runs checks and creates its own manifest and .vxgame. A supplied manifest.json is untrusted and does not replace server-generated metadata.

Installation

Agent receives only eligible published artifacts. The installed container layout is not a mandatory source-ZIP layout. Keep identifiers stable across releases. Use a VORIVOX namespace such as com.vorivox.game.reaction.