Templates & editing

Clicker and Merge support their respective economy or board settings; Runner supports its route, speed curve, and finish distance; Tower Defense supports costs, waves, damage, and base health. Every confirmed change creates a versioned running configuration you can test immediately.

All four templates can export a standalone HTML game or a self-contained TypeScript/H5 project with editable configuration, runtime source, build setup, deterministic rules, palette, and approved background or primary-object artwork embedded.

For every playable template, approved uploads now render in the live prototype and in its exported source: background artwork changes the playfield, while primary-object or tile artwork changes the interactive object where that template supports it.

When the deployment configures an OpenAI-compatible image provider, an editor can generate one bounded raster image for a selected runtime role. It is private to that project and follows the identical proposal approval, versioning, export, and source-sync path as an upload; audio generation is not included.

Before sharing a version, the workspace runs a Web release check for its design brief, deterministic runtime evaluation, version-bound asset manifest, and H5 handoff. Passing it lets you download the HTML or create an immutable web share.

The workspace handoff separates the same version into design rules, development implementation work, and art or asset requirements, so reviewers do not have to reconstruct scope from a generic specification.

The workspace also runs a synthetic balance sweep: Clicker tests fixed tap-rate profiles, Merge and Runner test deterministic seeds, and Tower Defense checks opening affordability and clear time. It is explicitly a rule simulation, not player analytics or a completion forecast.

Exported runtime changes also pass a Playwright browser smoke gate before they reach main. It boots Clicker, Merge, Runner, and Tower Defense standalone HTML exports, performs a representative interaction in each, and loads a compiled source-project export. This is repository-level regression evidence, not a forecast of an individual project version's player results.

An owner can also create a GitHub repository or update an existing one with the version-bound editable source, Game Spec, and asset manifest. The access token is used only for that request and is never written to project storage, browser storage, or version history.

The same version can also be downloaded as a native Canvas ZIP for WeChat Developer Tools. It includes game.js, game.json, project.config.json, a small touch/storage/asset adapter, and editable runtime source; it does not include AppID, credentials, payments, ads, or automatic publishing, so the owner must configure and validate the platform release.

Automatic publishing, AppID management, payments, ads, cloud services, and platform compliance checks are not built. They are never silently simulated by an exported project.