Underground 2 Revived
Play Need for Speed: Underground 2 (2004) in Chrome and Firefox with WebGPU graphics, Web Audio, up to 120 fps widescreen, controller support, free roam and Online races with friends. Fan project, not
Your campaign's living memory.
Translation pending
GamesTypeScript · CSSGitHub @jordan-romeroOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Hearth — a permission-filtered D&D campaign memory you can talk to.
Translation pending
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
A D&D Discord bot backed by a permission-filtered campaign memory you can
talk to — and a rich, themed campaign page behind login. The bot is the primary
interface; the memory is the substance; the fog-of-war permission filter is the
spine.
TypeScript · pnpm + Turborepo · Supabase Postgres + pgvector + Storage · Prisma ·
Auth.js (email + Discord) · Next.js/Vercel · Discord.js/Railway · pg-boss ·
Anthropic SDK · Groq Whisper (→ Deepgram/AssemblyAI) · Stripe.
Full rationale: ~/.claude/plans/campaign-memory-playful-stearns.md.Read the full README ↗A D&D Discord bot backed by a permission-filtered campaign memory you can talk to — and a rich, themed campaign page behind login. The bot is the primary interface; the memory is the substance; the fog-of-war permission filter is the spine.
hearth/
├─ apps/
│ ├─ web/ Next.js (Vercel) — campaign page, web API, Auth.js [Phase 5]
│ ├─ bot/ Discord.js (Railway) — capture, live Q&A, DM prep [Phase 1/2]
│ └─ worker/ Node (Railway) — pg-boss consumer: transcription, agents [Phase 2]
├─ packages/
│ ├─ db/ Prisma schema + client (single source of the schema) [Phase 0]
│ ├─ core/ ★ the permission filter + knowledge-unit domain ★ [Phase 0]
│ └─ agents/ Claude workflows (extract, classify, retrieve, prep) [Phase 1/3]
TypeScript · pnpm + Turborepo · Supabase Postgres + pgvector + Storage · Prisma · Auth.js (email + Discord) · Next.js/Vercel · Discord.js/Railway · pg-boss · Anthropic SDK · Groq Whisper (→ Deepgram/AssemblyAI) · Stripe.
Full rationale: ~/.claude/plans/campaign-memory-playful-stearns.md.
Phases 0-5 are merged: permission model, bot memory + capture, live sessions (incl. live transcription), NPC generation, and the campaign web app (ask, memory/codex, journal, DM library, corrections, share flow).
Next, per docs/scope.md's "Interactive page" list, the still-unbuilt pieces:
RELATIONSHIP knowledge units already model this;
it just needs a graph view.Map/MapPin tables yet).Session + provenance; no schema change needed).pnpm install
pnpm db:generate # after schema models exist
pnpm test # runs the permission-filter guard suite