Other engines integration
Native Other engines setup, integration source and export guidance.
Downloads for this guide
Other engines source packageSource + configuration/adapter + README; engine verification notes included.Download adapter.jsIndividual native integration source.Support and prerequisites
Integration source adapter; the native editor/export has not been verified. Validate your actual build under Play Island's sandbox before submission. The same per-game event registration and provider approval requirements apply. Download the source package and read README.txt before building. Browser samples never need a secret key.
Set up the project
Use a browser-capable HTML5/WebAssembly export running in the same window as the injected SDK. Load client.js before your controller, import IslandIntegration from adapter.js and await connect(), beginRun(), checkpoint(percent) and finishRun(score) at real transitions. Those names belong to this local helper, not the SDK. Catch errors and stop on rejection. Worker-only, native desktop/mobile, Electron and console integrations are unsupported by this browser adapter. A custom engine must independently verify its sandbox, storage, network and runtime requirements.
Native integration example
// Custom browser engine: call these from your real gameplay transitions.
export class IslandIntegration {
async connect() { this.configuration = await window.PIExample.connect(); return this.configuration; }
async beginRun() { return window.PIExample.report('started',{}); }
async checkpoint(percent) { return window.PIExample.report('progress',{progress:percent}); }
async finishRun(score) { return window.PIExample.report('completed',{score,progress:100}); }
async loseRun(score) { return window.PIExample.report('failed',{score}); }
}
// Include client.js. Catch rejected promises in the game's UI. These helper
// names are local conveniences; only window.PlayIsland is the platform SDK.Event lifecycle and errors
The project uses the supplied client.js helper to call the real injected PlayIsland SDK. It waits for configuration and acknowledgement callbacks. The helper serializes reports, detects rejected events and stops after a timeout or rejection. It does not manufacture accepted events offline. The example's proposed registry permits score (integer 0–1,000,000) and progress (number 0–100); both are optional in that proposal. Staff must publish the relevant definitions for your game. Other games may have different required fields. Do not copy a built-in game's specialized counters. Wait for real gameplay before reporting completion; the server rejects completed within the first three seconds of a session. Stop after terminal acceptance; use started to begin a new run or reload the launcher. On error, display the reason, correct the problem and reload to obtain a clean sequence.
Test, export and submit
- Test the engine's own rendering and controls locally. A standalone/editor launch will not connect to Play Island.
- Build using the setup instructions above and inspect the resulting runtime files.
- Follow ZIP packaging and provider submission.
- Use the visual preview for loading/layout. Use a published /play/ launch for actual accepted-event tests.
- Verify configuration, accepted start/progress/result, guest behavior, signed-in receipts if configured, replay and mobile controls.
Saves, exit, platform leaderboard navigation and general player profiles are not available automatically to your new game. See feature availability before adding those buttons.
Engine reference
Browser postMessage explains the native engine/browser mechanism. The Play Island contract is defined by the platform implementation, not by the engine documentation.