Browser Game · Portfolio

Detroit Dash

A daily one-shot dodge-runner. One button. One course a day, same for everyone.

Status
Live
Live: v3.1 — daily roguelite, replay-verified leaderboard, cosmetics
100%
Features listed below
7
Tools in the stack
7

No. 01 / The problem

What pain does this solve?

A portfolio needs proof of engineering depth, not just screenshots. Most "games" people ship are either trivial or lean on a heavy engine that hides the actual work. And any score leaderboard on a client-scored game is trivially forged — a naive high-score POST is worthless. The interesting problem is building something genuinely fun and habit-forming that also demonstrates real-time systems, deterministic simulation, and a trust model that holds up.

No. 02 / The solution

How the tool works

Detroit Dash makes determinism the product. The day key seeds the entire course, so everyone truly plays the same puzzle and scores are comparable. That same determinism powers a trustworthy leaderboard: players submit their input timeline (not a score), and a Cloudflare Worker re-runs the identical engine to compute the authoritative result — a forged score is impossible. The game grows through versioned releases (v1 basic runner to v3 daily roguelite with power-ups and cosmetics), each gated by a pinned determinism keystone test so the "same for everyone" guarantee can never silently drift.

  • One-button daily runner — same seeded course for every player, one shot per day
  • Deterministic simulation: America/Detroit day key seeds a mulberry32 PRNG driving every obstacle
  • Pixel-art Detroit skyline (Renaissance Center, Guardian, brick riverfront) with day/night by local time
  • Roguelite layer: escalating segments, one-button choice gates, and power-ups (shield, magnet, slow-mo, 2x)
  • Streak-combo scoring, Detroit-icon bonus collectibles, cosmetic skins + trails
  • Replay-verified global leaderboard — the client submits inputs, the server recomputes the score
  • 86 headless tests (node --test) pinning the deterministic course; no test framework

No. 03 / Technical approach

Architecture decisions

Vanilla JavaScript ES modules and a single <canvas> — no framework, no build step, served straight from GitHub Pages. The engine is pure and DOM-free: a fixed-timestep loop, a mulberry32 PRNG seeded from the Detroit day key, seeded world generation, AABB collision, and a shared session module that the live game and the server replay both drive so they can never disagree. The leaderboard is a Cloudflare Worker + KV that imports the same engine to replay-verify submissions. Tested with 86 headless node --test cases, including a keystone that pins an exact score for a fixed seed and input timeline.

  • JavaScript
  • HTML5 Canvas
  • ES Modules
  • Cloudflare Workers
  • Cloudflare KV
  • GitHub Pages
  • node --test

No. 04 / Current status

Where things stand

Live: v3.1 — daily roguelite, replay-verified leaderboard, cosmetics100%

No. 05 / Building something similar?

Recognize this problem in your own business?

This project started as a real frustration Ryan observed working inside companies. If you're dealing with a similar problem, let's talk. The solution might already be in progress, or we build it together.

Or text or call (248) 882-9055