Frequently asked questions
Clear answers about accounts, engines, events, rewards and publishing.
Do I need an account to read documentation?
No. Articles, event schemas for published games and generated downloads are public. Provider submission requires authorized creator access and an active assigned provider profile.
Is there an npm package to install in every game?
No public package distribution is implemented here. Hosted releases receive window.PlayIsland automatically. The downloadable declaration file describes it; client.js is an example helper, not a replacement platform SDK.
Can I use Unity or Godot?
Browser exports can use the bridge through native interop. Godot games already exist in the codebase. This center supplies native projects and honest validation notes; Unity and each new engine export still need compatibility testing under the actual sandbox.
Which events are mandatory?
There is no universal enforced event set for every game. Published per-game schemas, specialized validators and configured features determine requirements. The starter uses started/progress/completed; all must be registered. A terminal event is necessary to close a run immediately and support the normal replay flow.
Does completed award coins or XP?
Not by itself. Account eligibility, published server rules, caps and worker processing decide rewards. Guests receive no account grants.
Can the game identify the player or store progress?
There is no general player-profile API. Configuration provides session/game context and optional room context. Save methods currently work only for named bundled games; they are not a universal service for external submissions.
Can I test events in the package preview?
The provider preview is a visual package check and expires after 15 minutes. It has no normal gameplay parent responder. Use an approved published /play/ launch for real event testing; there is no general external-developer sandbox.
Can I upload my Unity/Godot source ZIP?
No. Downloaded native sources are for editing and exporting. Submit the exported browser runtime with root index.html and accepted asset types.
Are external URLs supported?
Staff can stage an HTTPS URL on an allowlisted host. Automatic SDK injection is limited to hosted packages. An external deployment needs a separately agreed integration and is not covered by the turnkey source-package path.
Why does a valid event fail after an earlier error?
The SDK increments sequence when sending, while the server increments only after acceptance. A rejection creates a gap. The example stops rather than silently sending more. Fix the problem and reload the launcher.