Play Island example sources — 2026-10-27

These examples use the existing injected window.PlayIsland SDK. PIExample is an
acknowledgement-aware SAMPLE helper, not a new SDK or a local acceptance simulator.
No production credentials are included or needed in browser games.

Before testing:
1. Ask the Island team for creator access and an active provider profile.
2. Ask authorized staff to review and publish event-definitions.json for YOUR game
   in the event registry. The JSON file does nothing by itself; each definition
   must be published through the existing registry UI. New games are not auto-registered.
3. Prepare a browser build as described below. Source ZIPs are NOT upload ZIPs.
4. Save metadata/version, upload the build in /provider, open the visual package
   preview, and submit for review. That preview has no gameplay session responder.
5. After approval/publication, use /play/YOUR-SLUG to test acknowledgements with
   real gameplay. Never infer rewards from accepted events. Guest sessions earn
   no account rewards; signed-in rewards depend on server rules and caps.

Keep index.html at ZIP root and include a <head> tag for SDK injection. Bundle
assets locally. No JavaScript eval, same-origin privilege, arbitrary network,
service worker or cookie access is promised. Disable precompression unless the
current delivery stack explicitly supports it (.br/.gz/.unityweb are not allowed).
The core example requires only started/progress/completed; vanilla also shows
paused/resumed/score. All must be registered. Do not send extras or per-frame events.
Completion must occur at least 3 seconds after the server session starts; samples
wait 4 seconds after accepted start. SDK V2 sequences are strict. Reload after
rejection/timeout: blindly sending the next report creates an out-of-order error.

Saves, exit and leaderboard navigation are currently allowlisted to bundled games;
do not assume a new game can call those APIs. No universal player/profile API exists.
This source is reusable under the included MIT license. Engine dependencies retain
their own licenses and must be installed separately where specified.

Guides: /developers/docs · Live schemas: /developers/docs/event-registry
Standalone browser/editor play cannot verify platform communication.

Unity setup

Open the extracted folder in Unity Hub using Unity 2022.3 LTS (project marker 2022.3.62f2) with Web build support installed. The supplied C# MonoBehaviour creates the sample controls. Choose Play Island → Build Web example: the editor command creates Assets/Example.unity and exports Build/. It selects the included PlayIsland Web template and disables compression and WebGL data caching (CacheStorage is unavailable in the sandbox). Keep client.js alongside index.html. No editor assembly or project source belongs in your submitted ZIP. This project compiled and exported successfully with Unity 2022.3.62f2 WebGL. Test your exported build under the platform sandbox and on the devices you support before shipping.

Engine reference: https://docs.unity3d.com/2022.3/Documentation/Manual/webgl-interactingwithbrowserscripting.html

Verification: Verified in local desktop and mobile-viewport Chromium: the exported starter loaded inside Play Island's real sandbox and completed a run with accepted start, progress and completion events. HTML5 also passed pause/resume and replay. This is not certification for every engine version or physical device.
