Lane Runner (DeepSeek V4 Flash)

1-shotVerified One-Shot
Screenshot
Play
Create a 3-lane endless runner as ONE self-contained HTML file.
Genre: auto-run forward; dodge obstacles in left/center/right lanes.
Lanes: 3 vertical lanes; player snaps to lane centers.
Controls: left/right or A/D to change lane; down or swipe down to slide under (optional).
Obstacles: barriers, gaps, low/high types requiring jump or slide if implemented.
Jump (optional): short arc to clear low obstacles — keep readable on mobile.
Score: distance or time survived; speed increases gradually.
Collectibles: coins optional for bonus points.
Collision: hit obstacle = game over; brief feedback.
Camera: side or behind angle — obstacles approach from ahead/right scroll.
Touch: lane buttons or swipe left/right.
Title + game over screens; restart without reload.
First 3 seconds easier spawn rate.
Obstacle patterns must be dodgeable — no unavoidable combos.
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

ModelDeepSeek V4 Flash
AgentOpenCode
Prompt Count1
Human Edits0
RuntimeSingle HTML
Vote

Challenge

Endless Runner
Fork Prompt

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