You are integrating the Buncha Games SDK into my approved closed-beta browser game.

Prefer window.buncha when available. Treat window.galaxy as a temporary legacy alias only if the current runtime still exposes it. SDK calls must fail soft when the Buncha Games wrapper is absent.

For browser JavaScript or TypeScript games, install @bunchagames/sdk and import { buncha } from "@bunchagames/sdk". Use installLocalBunchaMock() only for local development/testing when window.buncha is absent. For Unity WebGL projects, use the Buncha Games Unity UPM tarball. For Godot Web projects, use the Buncha Games Godot addon ZIP. Do not hand-write postMessage code unless Buncha Games explicitly asks for a custom integration.

Unity, Godot, and other engine builds can deploy on Buncha Games without SDK hooks. When you add custom events, use the Buncha Games adapter for that engine or a JavaScript bridge that fails safely when the Buncha Games wrapper is absent.

Add only safe lifecycle analytics:
- ready,
- game start,
- game end,
- small custom events.

For identity-aware UI or an existing game-owned save/leaderboard flow, call window.buncha.player.getProfile() before the player starts the run/match/save flow. If signedIn is true, use profile.displayName and profile.id as the authoritative playerName/playerId and lock the in-game display name so stale local names cannot be submitted. If signedIn is false or the SDK is unavailable, keep the normal local/guest name-entry fallback. This closed-beta SDK prompt does not define a public Buncha Games cloud-save or leaderboard API.

The profile response exposes only signedIn, profile.id, profile.displayName, and profile.avatarUrl. Do not request or assume email, auth ids, developer/admin status, private account fields, legal status, monetization eligibility, or payment data.

Do not add wallet, IAP, entitlement, ad, checkout, payout, or other commercial-shaped interfaces from public documentation. Approved testers receive separate protected instructions when a bounded non-payable Sandbox QA task is authorized.

Do not add secrets, external ads, external payments, crypto, provider SDKs, payout logic, or production monetization assumptions. The game must continue to run locally when the Buncha Games wrapper is absent.