Overview

This section is a set of complete programs. Each page shows every file the build it describes consists of, whole, so the engine’s surface can be judged from working code. Every file compiles against the types the APIs section declares.

Each build has the same shape. index.html is the page the build is served as, src/main.ts creates the engine and boots it, src/game.ts exports the Game<S, D> the engine drives, assets/ holds the files the game loads, and tests/ holds the vitest suites a case checks the build with.

index.html
src/main.ts
src/game.ts
assets/
tests/

The boot sequence is the same on every page as well: construct the engine, subscribe to anything the caller wants to observe, initialize, and run.

const engine = createEngine({ canvas, width, height, game });
await engine.initialize();
await engine.run();

Pages

Page	Shows
A Minimal Game	The smallest complete build: a page, a boot module, and a game that moves a rectangle by the frame’s delta.
Input and Actions	Registering a touch layout’s vocabulary, reading a held analog action and a digital edge, and driving the same code from a key and from a test.
Audio and Assets	Loading a sprite and a produced audio file during initialization, playing a synthesized cue and a file-backed cue, and surfacing a failed load.
Diagnostics and Overlay	Registering overlay sources during initialization and reading them back while the game runs.
Validating a Game	A vitest suite that imports the build’s own game, steps it with engine.advance, and checks pixels and draw calls.
Scripted Clocks	One scenario stepped under a constant, a repeating sequence, and a seeded jitter clock.