Dungeon Crawl (Qwen 3.5 9B)

1-shotVerified One-Shot
Screenshot
Play
Create a roguelike dungeon crawl (single floor) as ONE self-contained HTML file.
Genre: top-down grid dungeon; explore rooms; fight monsters; find exit.
View: tile map 15×15 or multi-room layout with fog optional.
Player: HP, simple melee attack adjacent tile or bump-to-attack.
Monsters: 2 types — slime (weak) and skeleton (tougher); chase on sight.
Loot: potion heals HP; key opens exit door.
Exit: reach stairs tile to win.
Death: HP zero = game over; restart run.
HUD: HP hearts, floor label, keys count.
Keyboard: arrows move turn-based OR real-time simple — pick one and document.
Touch: swipe or D-pad.
One floor enough; no persistent meta between runs required.
Rooms connected — no unreachable exit.
Damage numbers or flash feedback.
Minimap (optional) corner.
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.
Stack

ModelQwen 3.5 9B
AgentOpenCode
Prompt Count1
Human Edits0
RuntimeSingle HTML
Vote

Challenge

Roguelike Dungeon
Fork Prompt

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