KBBQ Idle WebGL

Recruiter-facing proof path for a playable idle game: confirm the build is healthy, show the core economy loop, then explain why the WebGL surface is safe to host publicly.

01 · Build health

Check the uploaded WebGL bundle before making any “playable” claim.

02 · Core loop

Explain grill → serve → upgrade → prestige as one clean economy story.

03 · Public posture

Use compliance and policy pages before discussing ads or rollout.

First reviewer path

1 · Frame it: confirm whether the build is intentionally absent or ready for preflight.
2 · Verify: use Check Build Files before making any playable claim.
3 · Defend: open Help / Compliance to explain rollout checks and public guardrails.

This primary panel stays intentionally docs-first until a verified Unity WebGL build is attached. If a real build exists under docs/Build/, set the build name below (for example KBBQIdleWebGL) and run preflight before starting it.

Reviewer handoff

Use this to narrate the current state without overstating whether the build is actually live.

Current mode

Docs-first review

Playable claim

On hold until preflight and launch succeed.

Next move

Run Check Build Files before any playable claim.

Evidence note

Build verification and live launch are intentionally kept separate.

Ready to summarize the current reviewer posture.

Ready. Click Start Game after uploading WebGL build artifacts.

Tip: if your build uses `.unityweb`/`.br`/`.gz`, this page auto-detects those formats. Keyboard: C check · S start · F fullscreen · B copy checklist · ? help.

Reviewer placeholder · build not loaded

The playable build is intentionally not assumed to be live.

Use this restrained pass to show reviewers what should happen next: verify the build bundle, explain the loop with the docs pages, and keep rollout language honest until preflight passes.

Base KBBQIdleWebGL

Mode Docs-first review

Claim No fake playable promise

What reviewers can assess now

Docs route, controls copy, economy explanation, and release posture can be reviewed before Unity is live.

What still needs proof

A real playable claim still depends on preflight plus a clean WebGL launch.

Next recommended move

Run Check Build Files, then use Help and About as the reviewer script if the bundle is absent.

Evidence anchor

The panel below tracks manifest and core asset presence without pretending the game is already running.

Open rollout checklist Open gameplay overview Open public guardrails

Reviewer evidence board

Docs route ready

Build not yet checked

Playable claim on hold

Build/build-manifest.jsonWaiting for page check
Build/KBBQIdleWebGL.loader.jsVerify before launch
Build/KBBQIdleWebGL.data*Verify before launch
Build/KBBQIdleWebGL.framework.js*Verify before launch
Build/KBBQIdleWebGL.wasm*Verify before launch

What to verify before public rollout

Bundle present: loader, data, framework, and wasm files resolve from docs/Build/.
Reviewer route ready: Help, About, and Compliance explain controls, loop, and hosting posture.
Public claims held back: do not call this page playable until preflight and launch both succeed.

If build files are missing, this panel should remain as the honest primary state instead of reading like a broken black box.

Reviewer Path

1. If the playable build is absent, keep the placeholder visible and narrate the review route instead of implying a live game.
2. Run Check Build Files before claiming the WebGL surface is live.
3. Open Help and About to explain controls, loop, and deployment posture.
4. Use Compliance before discussing monetization or public rollout.

How to Play

Buy raw meat, place it on a grill slot, then flip and collect when it is ready.
Serve customers with cooked inventory to keep queue flow and income stable.
Use upgrades and boosts to speed up sizzle throughput and unlock better cuts.

Trust & Policy