jprty

Notes

Question (question, answer, points, (QuestionSetId)) (some questions will be imputed as the dataset is not complete) QuestionSet Question[] (year/date, title, tags[] (this will be generated from the question set)) Player Host Host State Player State Game State Room (code, Players[], Host) Accounts Leaderboard

Configurations Number of Players to Room Size Question Set types (tags) Question Set year (range) Question Set difficulty (?)

Buzz Window Response Window Answer Reveal Window

Screens

Settings screen (host only) pick categories, year range, difficulty, (later down the line allow people to upload/connect question sets)

Start screen (computer/default host/create a room)

Start screen join a room (enter room code, usually mobile)

Waiting screen (waiting for players to join)

Close queue: either the VIP player or the host can close the queue

Starting round

Categories description

Category picker screen (host or VIP player starts)

Question picked

Question being read, Buzz window for players

players that buzz in write ansewr

validate answer.

Continue until question answered or timer runs out or everyone answered.

Reveal Answer

Leaderboard/Points update

Continue until timeout, or all players have answered. (host can also end round early)

Continue until all rounds are done.

Display winner.

Room State

• Players (Host, Guest, Logged in, Active)
• Game State (Pending, Round, Buzzed)
• Room State (Waiting, Players, Etc)

SpacetimeDB migration

The live runtime direction is now SpacetimeDB-first for room/game state.

• spacetimedb/ contains the active backend/runtime module for live-room and gameplay state.
• apps/web is the deployed app surface (Vercel target).
• Server-side room provisioning, membership sync, and gameplay commands (start/select/buzz/answer) write to SpacetimeDB when SPACETIMEDB_URL and SPACETIMEDB_DATABASE are configured.
• Room/game snapshot reads use SpacetimeDB live tables (live_room*, live_game_*) through the web app tRPC layer.
• Production web runtime should be configured with:
  • NEXT_PUBLIC_LIVE_RUNTIME_BACKEND=spacetimedb
  • NEXT_PUBLIC_SPACETIMEDB_URL (SQL/read endpoint base, e.g. https://maincloud.spacetimedb.com)
  • NEXT_PUBLIC_SPACETIMEDB_DATABASE
• The docs/spacetimedb-phase*.md files are historical migration notes from pre-cutover slices. docs/vercel-spacetimedb-cutover.md records the current cutover sequence.

Local Postgres

• Copy .env.example to .env at the repo root.
• Start a local PostgreSQL instance on localhost:5432 with a jprty database and the postgres user.
• Run bun run --cwd packages/db db:migrate and bun run --cwd packages/db db:seed.
• Default seed data now uses OpenTriviaQA (CC BY-SA 4.0). See docs/question-bank-open-trivia.md.
• Postgres is limited to auth/users and relational app metadata.
• Vercel builds only run the Turbo build graph and Prisma client generation. Run bun run --cwd packages/db db:deploy once per release from a single deploy job or operator shell instead of from the parallel build graph.

Deploy Direction

• apps/web targets Vercel.
• spacetimedb/ is the source of truth for live rooms and gameplay state.
• Legacy Fly app-server deployment files were retired (fly.toml, Dockerfile).
• Multiplayer reducer smoke walkthrough: docs/spacetimedb-authoritative-multiplayer.md.

The DB package now loads the repo-root .env directly, so package-scoped commands such as db:seed do not require manual shell exports first.

Demo Video

• The PR #3 MP4 lives at artifacts/pr-3-spacetimedb-room-mirror-demo.mp4.
• Open artifacts/pr-3-spacetimedb-room-mirror-demo.html in a browser for a direct local video player.
• The full gameplay demo bundle for the current migration slice is documented in docs/spacetimedb-e2e-demo.md.