Downloads and example projects
Real source files, engine projects, runtime ZIPs and integration utilities.
Downloads for this guide
HTML5 runtime ZIPRunnable runtime files; event registration and approval still required.Integration toolsDiagnostics and server signing source.Choose a package
- Unity: source ZIP. Native project sources; export in the engine before submission.
- Godot: source ZIP. Native project sources; export in the engine before submission.
- HTML5 / JavaScript: source ZIP. Complete dependency-free example; separate upload ZIP below.
- Phaser: source ZIP. Buildable npm source project; install dependencies and run build.
- PixiJS: source ZIP. Buildable npm source project; install dependencies and run build.
- Three.js: source ZIP. Buildable npm source project; install dependencies and run build.
- Construct: source ZIP. Integration adapter and setup instructions; not a native project export.
- GameMaker: source ZIP. Integration adapter and setup instructions; not a native project export.
- PlayCanvas: source ZIP. Integration adapter and setup instructions; not a native project export.
- Other engines: source ZIP. Integration adapter and setup instructions; not a native project export.
Runtime versus source
Only vanilla-upload.zip is a ready-made runtime submission ZIP. Source packages include README.txt, compatibility notes, an event-definition proposal, license and native/build files. Unity/Godot must be exported; JavaScript engine projects must be built; Construct/GameMaker/PlayCanvas adapters must be added to your own project. The package validator correctly rejects native source file extensions in game uploads.
Individual resources
- SDK TypeScript declarations: generated from the actual public interface.
- Sample event definitions: staff-reviewed proposal, not self-installing configuration.
- Passive diagnostics: observes real acknowledgements/receipts.
- Server signing utility: server only, separately provisioned key required.
- Download manifest: file sizes and SHA-256 hashes for generated resources.
Verification scope
No package contains an account credential or production integration key. All engine examples use the existing SDK or a clearly named sample helper. Syntax and bridge validation are distinct from native compiler/export execution. The guide badges state whether engine validation remains pending. Verify the exact engine version and target browsers before using an example in production.