Help & Troubleshooting

Use this guide when the game does not start, saves look wrong, or deployment setup is unclear. If the Play page is still showing its reviewer placeholder, treat that as an honest missing-build state rather than a broken launch.

Quick Start

Open Play page and confirm build name (default: KBBQIdleWebGL).
Click Check Build Files and verify data/framework/wasm are all detected.
Click Start Game.
Press F or click Fullscreen for immersive mode.

What the Reviewer Placeholder Means

Docs-first, not broken

If the large Play panel still shows the placeholder, treat it as an honest waiting room for review rather than a fake or failed game surface.

Evidence board

The placeholder now lists manifest/core-file status and reviewer signals so you can explain what has been verified without pretending Unity is already live.

Claim boundary

Only call the page playable after both preflight and real launch succeed. Until then, keep using Help/About/Compliance as the front-door walkthrough.

Cloudflare Pages Deployment

Framework preset: None.
Build command: leave empty if committing prebuilt docs/Build assets.
Build output directory: docs.
If build artifacts are missing, run ./tools/build_webgl_docs.sh then push.

Common Problems

"Build check failed": verify that docs/Build contains .data, .framework.js, .wasm, and loader files.
Reviewer placeholder still visible: this is expected until preflight succeeds and the Unity loader starts cleanly; use the evidence board to show exactly what has or has not been confirmed yet.
Black screen after load: hard refresh to clear stale cached build files.
No ad shown: ad slot stays disabled until real AdSense client/slot values are configured.
Save issue: clear browser site data and restart session if local save is corrupted.

Reviewer Evidence Order

1. Read the placeholder badges/signals to see whether the page is in docs-first, checking, verified, or missing-build mode.
2. Use the file list to confirm which exact build assets were found for the current base name.
3. If the build is still absent, continue the review with About and Compliance instead of narrating a fictional live session.
4. If the build is verified, launch Unity and treat successful canvas takeover as the final playable proof.

Before Public Rollout

Confirm the Play page no longer relies on the placeholder because Check Build Files and Start Game both succeed.
Verify Help, About, and Compliance still match the shipped build and monetization posture.
Keep public copy honest: if the bundle is absent, describe the docs surface as a reviewer walkthrough, not a live build.

Need Support?

Open an issue at GitHub Issues with browser/device, screenshot, and reproduction steps.