Test and debug integration
Separate engine rendering, package preview, event acceptance and reward verification.
Downloads for this guide
Passive diagnostics utilityAttach to a real hosted game frame; no fake events.Integration tools ZIPDiagnostics, proposed schemas and server-only signing helper.Four different checks
| Test | What it proves |
|---|---|
| Engine/editor preview | Rendering and input in that environment; no platform acceptance |
| Provider package preview | Saved runtime loads in an isolated frame; no regular gameplay session responder |
| Published /play/ launch | Real configuration, session validation and event acknowledgements |
| Signed-in receipts | Actual configured server reward processing, after event acceptance |
There is no public self-service event sandbox or seeded external-developer test account. Staff have protected testing/simulation tools; these are not general browser SDK APIs. Do not publish synthetic reward activity into an ordinary player account and call it a dry run.
Observe without emitting events
Use the downloadable diagnostics utility inside the game's own frame. It subscribes to SDK acknowledgements/receipts and reads configuration. It sends no gameplay events. Select the game frame in browser developer tools; the top-level page does not expose the game SDK.
// Run inside a hosted game's own frame (not the top-level website console).
// Observes existing callbacks; sends no gameplay events and grants no rewards.
(() => {
if (!window.PlayIsland) { console.error('No injected SDK. Check the HTML <head> and launch URL.'); return; }
const offAck=PlayIsland.onAcknowledgement(ack => console.info('[Play Island acknowledgement]',ack));
const offReceipt=PlayIsland.onReceipt(receipt => console.info('[Play Island receipt]',receipt));
PlayIsland.getConfiguration().then(config => console.info('[Play Island configuration]',config)).catch(error => console.error(error.message));
window.stopPlayIslandDiagnostics=() => { offAck(); offReceipt(); delete window.stopPlayIslandDiagnostics; };
})();Practical acceptance sequence
Use the starter or real gameplay to reach an actual result. Expect monotonically increasing V2 sequences and accepted UUIDs. Check error text rather than just HTTP status; inspect Network for failed runtime assets and Console for CSP/storage violations. Reload after a rejected sequence. Verify pause doesn't emit per-frame traffic, completion waits at least three seconds and replay does not duplicate event handlers.
What to record
Record the engine/version, game slug, release ID, browser/device, event name, eventId, acknowledgement error and reproduction steps. Remove play tokens, integration keys and player personal information before sharing logs. Treat absence of a receipt differently from a rejected event: rules, caps, account eligibility or the worker can affect rewards.