Start integrating
The shortest path from a browser game to a reviewed Play Island release.
Downloads for this guide
HTML5 source projectNo engine dependency; includes setup and event schema proposal.Before you begin
Play Island hosts browser games in an isolated iframe. It injects a JavaScript SDK into hosted HTML and the parent launcher forwards gameplay reports to the server. The game does not receive an account cookie, account password or play token.
Your integration checklist
- Choose your engine guide and download its project or adapter.
- Prepare a local-asset browser export with index.html at the root and an actual HTML head element. Check sandbox compatibility.
- Ask staff to agree the event names and payload schema for your game. The sample event-definitions.json is a proposal, not automatic registration.
- Read configuration, report real gameplay transitions, and observe acknowledgements. A report accepted by the server is not a reward grant.
- Export and package only runtime files. Prepare the metadata and cover specified by the submission guide.
- Use the provider workspace to save, upload and visually preview a release. Submit the saved snapshot for staff review.
- After approval, open /play/your-slug and test guest and signed-in journeys. This creates real sessions; there is no general external-developer event sandbox.
Minimum sample flow
// PIExample is the downloadable sample helper, not a platform SDK method.
await PIExample.connect();
await PIExample.report('started', {});
// Real gameplay occurs here. Do not manufacture an instant completion.
await PIExample.report('progress', { progress: 20 });
// At the actual end, after at least 3 seconds of server-session time:
await PIExample.report('completed', { score: 50, progress: 100 });Each event above must be registered for your game. The generic validator does not impose a universal required-event list; your registered fields, game-specific checks, boards and reward rules define the contract. The recommended start/progress/result flow makes sessions understandable and allows replay.
What the starter proves
The HTML5 starter has real gameplay controls, the injected SDK handshake, ordered events, acknowledgements, pause/resume and replay. Other packages expose native engine entry points. Their verification status is described in each guide; an adapter is not an engine certification.