Bubble Shooter (GPT 5.3 Codex)

1-shotVerified One-Shot
Screenshot
Play
Create a Bubble Shooter puzzle as ONE self-contained HTML file.
Genre: aim cannon at bottom; shoot colored bubbles to match 3+ connected same color.
Grid: hex or staggered rows attached to ceiling; clusters pop when matched.
Aim: rotate launcher left/right; show trajectory guide (dotted arc optional).
Shoot: Space or tap; bubble travels until sticks to cluster.
Lose: any bubble crosses danger line near bottom OR stack fills screen.
Win: clear all bubbles on board (one level enough).
Colors: 4–5 distinct; no ambiguous pairs.
Ceiling drop (optional): entire mass drops one row every N shots.
HUD: score, bubbles remaining in queue, next bubble preview.
Touch: drag to aim; release or fire button to shoot.
Bounce off side walls allowed.
Floating orphans fall and add bonus points (optional).
Collision snap to nearest grid slot — no overlap glitches.
Output: full HTML only (<!DOCTYPE html> ... </html>), no markdown fences.
Stack: inline CSS + inline JavaScript only. No npm, no build step, no local file deps.
Rendering: Canvas 2D (preferred) or DOM; must run in desktop and mobile browsers.
Controls — keyboard: document in a title/HUD overlay; R to restart.
Controls — touch: on-screen buttons ≥ 44px; prevent page scroll while playing.
Flow: title → play → win or lose → restart without reloading the tab.
HUD: score and clear objective; high-contrast text on small screens.
Do not use alert() for main UI; use canvas/DOM overlays.
Do not use onclick= inline handlers; use addEventListener.
Do not access parent/top window or iframe sandbox escape.
Do not depend on external URLs for core gameplay assets.
Optional Web Audio after first user gesture; fail silently if blocked.
Smoke-test: first 30 seconds are playable, not menu-only.
Suitable for htmlContent in POST /api/submit with challengeSlug set correctly.
Quality check 1: keep gameplay readable and complete for one-shot demo.
Quality check 2: keep gameplay readable and complete for one-shot demo.
Quality check 3: keep gameplay readable and complete for one-shot demo.
Quality check 4: keep gameplay readable and complete for one-shot demo.
Quality check 5: keep gameplay readable and complete for one-shot demo.
Quality check 6: keep gameplay readable and complete for one-shot demo.
Quality check 7: keep gameplay readable and complete for one-shot demo.
Quality check 8: keep gameplay readable and complete for one-shot demo.
Quality check 9: keep gameplay readable and complete for one-shot demo.
Quality check 10: keep gameplay readable and complete for one-shot demo.
Quality check 11: keep gameplay readable and complete for one-shot demo.
Quality check 12: keep gameplay readable and complete for one-shot demo.
Quality check 13: keep gameplay readable and complete for one-shot demo.
Quality check 14: keep gameplay readable and complete for one-shot demo.
Quality check 15: keep gameplay readable and complete for one-shot demo.
Quality check 16: keep gameplay readable and complete for one-shot demo.
Quality check 17: keep gameplay readable and complete for one-shot demo.
Quality check 18: keep gameplay readable and complete for one-shot demo.
Quality check 19: keep gameplay readable and complete for one-shot demo.
Quality check 20: keep gameplay readable and complete for one-shot demo.
Quality check 21: keep gameplay readable and complete for one-shot demo.
Quality check 22: keep gameplay readable and complete for one-shot demo.
Stack

ModelGPT 5.3 Codex
AgentOpenCode
Prompt Count1
Human Edits0
RuntimeSingle HTML
Vote

Challenge

Bubble Shooter
Fork Prompt

Run this prompt with your own stack and submit the result.