Flappy Flyer (GPT 5.4 Mini)

1-shotVerified One-Shot

Screenshot

Play

Create a Flappy Bird–style endless flyer as ONE self-contained HTML file.
Genre: tap/click to flap upward; gravity pulls down; pass gaps between pipes or obstacles.
Single-button core: Space/click/tap flaps; release does nothing extra.
Obstacles: evenly spaced gaps; scroll world left; random gap Y within safe bounds.
Score: +1 per gap passed; show current and best score.
Collision: hit pipe/ground/ceiling = game over; brief freeze then restart overlay.
Difficulty: constant scroll speed or gentle ramp every 10 points.
Visual: simple bird sprite or shape; day-sky palette readable on mobile.
Parallax background optional (clouds) — must not hurt performance.
Touch: full-screen tap; prevent scroll.
Title screen with start; game over with retry.
Fair hitboxes slightly smaller than art.
First pipe appears after 1s warmup.
No impossible gap heights.
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.4 Mini

AgentOpenCode

Prompt Count1

Human Edits0

RuntimeSingle HTML

Vote

Challenge

Flappy Endless

Fork Prompt

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