Prepare a compatible game
Sandbox, storage, network and export constraints enforced by the current platform.
Browser and packaging requirements
Your game must run in a browser and use local paths for its packaged runtime assets. Include index.html at ZIP root and a real head element for SDK injection. Responsive canvas/UI, readable controls and a user gesture before audio are practical compatibility recommendations; the package validator does not measure usability or frame rate.
The sandbox
The frame permits scripts and pointer lock, without allow-same-origin. Its origin is opaque. Do not rely on document cookies, direct localStorage, IndexedDB, service workers or same-origin access to the Play Island parent. Request state through supported SDK methods only; general-purpose saves are not enabled for new games. The content security policy permits WebAssembly compilation but not JavaScript eval/new Function. Dynamic code-generation engine features must be disabled or verified. Network connections are limited to the current immutable release asset path and staff-approved HTTPS/WSS origins. A CDN dependency that works on your own website may fail here; bundle it locally.
Engine export considerations
- Godot: use Compatibility rendering, single-threaded Web export and no PWA. Keep .wasm and .pck beside the generated index.html.
- Unity: disable compression and data caching for the supplied template. .br, .gz and .unityweb are not package-allowed extensions. .wasm, .data and .js are accepted. Unity runtime compatibility still needs an exported-browser test.
- Construct: the supplied adapter requires DOM mode (Use worker = No). It cannot see the injected window SDK from a worker.
- JavaScript engines: bundle dependencies and avoid dev-server URLs in the final artifact.
Network and multiplayer
An approved connection is an origin such as https://your-game-server.example or wss://your-game-server.example, without custom ports, credentials, path, query or fragment. Private/local hosts and the platform hostname are excluded. Only staff-approved connections affect delivery policy; a game cannot authorize its own origin by sending a message. Room context does not provide a complete multiplayer transport. Implement and validate your own compatible game protocol; do not treat a room code or playerId as general account authentication.