Game integration guide

Choose an integration path

External submissions are already-hosted HTTPS web games. Submit a playable URL, cover, description, controls and version for review. Approved games open on their original website. Uploading source, ZIP files or built bundles is not supported.

SDK integration is a separate workflow coordinated with the site maintainer. It connects registered games running in the site player to user state, lifecycle events and account saves. Adding the SDK script or inventing a game ID does not enable account access.

Integration steps

1. Agree on a stable game ID, build version, resource path and save format with the maintainer.
2. Integrate the SDK and verify local saves in standalone mode.
3. Have the maintainer register the game in the catalog and load it through the site player.
4. Test signed-out, signed-in, offline, conflict selection and restoration flows before release.

SDK quick start · Save behavior · Submission process

Release checklist

Support desktop and mobile input; provide loading errors; serve resources over HTTPS. Pause timers, audio and input on pause, and avoid starting duplicate loops on resume. Restore saves before gameplay starts and update the running state when another save is selected. Keep the game ID stable and migrate older save schemas. Do not put credentials or unrelated personal data into saves or events.

Documentation and community

The knowledge base hosts maintained integration docs, controls and curated guides. Use the player discussion entry on each game page for questions, strategies and feedback. Useful conclusions can then become maintained knowledge-base articles.