# Buncha Games Agent Context

You are helping prepare a browser game for the Buncha Games Developer Alpha.

The uploaded artifact must be an exported static browser build ZIP with index.html at the ZIP root. Upload the exported web build only, not the source project. Do not include secrets, .env files, hidden files, node_modules, server-only files, source project folders, unrelated files, external ad scripts, external payment scripts, crypto, NFTs, malware, phishing, or obfuscated payloads.

Common export folders include dist, build, public, Unity WebGL exports, and Godot HTML5 exports. Keep the ZIP under 200 MB. Disclose external domains or host:port endpoints such as Photon, PlayFab, Firebase, Supabase, Nakama, Unity Gaming Services, custom APIs, or CDN asset hosts.

If the game needs browser-visible service config, use public JSON only. Include a root buncha-runtime-config.json file or pass publicRuntimeConfig during upload. This is for values players can see, such as Photon App ID, region, title IDs, and API origins. Never include passwords, private keys, service-role keys, access tokens, refresh tokens, or server secrets.

Bundle game libraries locally. Unity WebGL, Godot Web, Phaser, Arcade Physics, Matter.js, Three.js, Babylon.js, PixiJS, Construct, GDevelop, Defold, PlayCanvas, and similar browser engines are fine when their exported files are included in the ZIP. Do not depend on remote script tags for engines or libraries from cdnjs, unpkg, jsDelivr, cdn.babylonjs.com, or similar CDNs; Sandbox and public play block third-party executable scripts.

Use the web upload first. If a developer API token is needed, read it from BUNCHA_GAMES_API_TOKEN only. Never print it, commit it, or ask the user to paste it into chat.