Dad's Annual Game Bounty Hunt

A single-file, config-driven web app for running a yearly "video-game bounty hunt" — a parent posts classic games with cash rewards; a kid captures the bounties by beating them. Everything lives in one index.html with no build step; state is stored in the browser (localStorage) and backed up via JSON/CSV export.

First run

A browser with no saved board gets a short setup: board title, the player's name, an optional Manage PIN and the default bounty, with a choice to start from the 10 classic games or an empty board. Dad's Annual is a one-tap preset that fills in the original board; Import a backup instead restores a JSON backup. Browsers that already have a board skip it.

Two modes

• User (play) — the default. The kid sets each game's outcome and watches the stats:
  • Complete — won it (confetti + "BOUNTY CLAIMED").
  • Withdraw — didn't get to it; can come back next year (muted card).
  • Reject — tried it, not for them; won't be reused ("GAME OVER / womp womp").
• Manage (edit) — locked with a 4–8 digit PIN (padlock button). Once unlocked, every grown-up action is in the Manage menu next to the padlock, and each card has its own menu (☰) to edit, reorder or delete that game. Grown-ups can:
  • Edit the title / eyebrow / season / year / kid name / default bounty.
  • Add, edit, reorder, and delete games (up to 99). Bounties default to $25.
  • Auto-fill a game's details from RAWG + a Wikipedia reference link (needs a free RAWG key, set in Manage → Settings).
  • Import / export the board as JSON (full backup or one season) or CSV (games).
  • Close out a season, archiving it to the History tab and starting a fresh board (optionally carrying withdrawn games forward).

The PIN is a speed-bump, not real security — it's stored in the browser. Take a JSON backup (Manage → Import / Export → Full backup) before each season as your safety net.

Run locally

Any static server works. For example:

python3 -m http.server 4177

Then open http://localhost:4177/. You can also just open index.html directly (file://) — only the RAWG/Wikipedia auto-fill needs a network connection.

Deploy (Cloudflare, auto-deploy on push)

Live at https://game-bounty-hunt.nineafterten.com. Cloudflare builds the repo on every push to main: build command npm run build, deploy command npx wrangler deploy. The build copies only index.html and _headers into dist/, which wrangler.jsonc serves, so legacy/ and the repo's other files are never public. _headers keeps the board out of search results.

The old game-bounty-hunt.netlify.app address only redirects: netlify-redirect/_redirects was deployed once with netlify deploy --prod --no-build --dir netlify-redirect --site game-bounty-hunt.

Board data lives in each browser, per address. To move it, use Manage → Import / Export → Full backup on the old address, then import it on the new one with Replace.

Versioning

Semver lives in package.json and in APP_VERSION inside index.html (shown in the footer). To cut a release: npm version patch (bumps + git-tags), bump the matching APP_VERSION, then git push --follow-tags.

Files

• index.html — the whole app (HTML + CSS + JS).
• legacy/bounty-hunt.html — the original 2026 version, kept for reference.
• wrangler.jsonc, _headers, package.json, .gitignore — deploy + tooling config.