The Golden Ball broadcast you see on the game page runs inside a security-restricted frame β the same embed-friendly delivery the platform is designed around. The frame is intentionally minimal: it shows the game, reports its own state honestly, and grants the embedded content no more capability than it needs.
The frame bar
Above the broadcast sits a control bar with three actions. Refresh reloads just the game, without leaving the page. Fullscreen expands the whole broadcast area using the pageβs own fullscreen control. The Embed action opens the embed dialog: it produces a snippet for the canonical Community embed URL and states the one remaining gate β the partner domain must be approved before the frame will load on that site.
Status indicators
- Connecting β the frame is loading; a hard timeout prevents an indefinite spinner.
- Frame Loaded β the game document finished loading inside the frame.
- Error β the frame could not load in time; a Retry control appears.
- Not-connected state β when no game URL is configured, an honest placeholder panel says so rather than mounting an empty frame.
Security posture, in plain words
The frame runs sandboxed with the minimum capabilities a cross-origin game needs, and no extra permissions β the game never asks for camera, payment, popups or similar, so none are granted. The page and the game also never exchange your data; the frame is a viewing window, not a data channel.
When the connection drops
If the game host becomes unreachable, the frame shows its error state with a Retry action, and the results area shows its own unavailable notice. When the game returns, a Refresh (or the automatic next page load) restores the broadcast β no reinstall, no cache clearing, no waiting on a redeploy.