After Hours Burger
A first-person cooperative burger restaurant for the web. One to four cooks share a late-night
kitchen: customers walk in and order at the counter, and the cooks grab ingredients, turn the
grill knobs, flip patties with a spatula, melt cheese, squeeze the right sauces and serve each
customer the burger on their ticket, built from memory. Works with mouse and keyboard and
with iPad touch controls, in the same room.
Status: Stage 1 (real multiplayer interaction slice) is playable, with Stage 2
(persistence and recovery) foundations and a Blender-authored art pass: a modelled restaurant
with Cycles-baked global illumination and reflection probes, food whose cooking state drives
its shader, stocked props, skin-textured first-person hands, and rigged teammates and walk-in
customers. All art is generated by code
in assets/source/blender (see docs/ASSET_PIPELINE.md). See
docs/PLAN.md and docs/KNOWN_LIMITATIONS.md.
Install on your VPS
Full guide: docs/DEPLOYMENT.md. The short version, on Ubuntu/Debian
with two DNS records (game. and realtime.) pointing at the VPS:
curl -fsSL https://get.docker.com | sudo sh
git clone https://github.com/w1nofgood/burgurgame.git /opt/after-hours && cd /opt/after-hours
cp deploy/.env.example deploy/.env # set POSTGRES_PASSWORD, GUEST_TOKEN_SECRET, ALLOWED_ORIGINS, VITE_REALTIME_URL
docker compose -f deploy/docker-compose.yml --env-file deploy/.env up -d --build
scripts/build-client.sh https://realtime.example.com /var/www/after-hours/client
# then Nginx + Let's Encrypt (deploy/nginx/after-hours.conf), or your DirectAdmin panel
scripts/smoke.sh https://realtime.example.com https://game.example.com
Windows Server VPS? Follow docs/DEPLOYMENT_WINDOWS.md: copy-paste
PowerShell that installs Node.js, PostgreSQL and Caddy (automatic HTTPS) as Windows services, plus
scripts/windows/update.ps1, backup.ps1, restore.ps1 and smoke.ps1.
Do you need DirectAdmin or a separate static host? No. The same VPS serves the static
website (via Nginx) and runs the game service and database in Docker. If your VPS already uses
DirectAdmin, the guide shows how to use its web server instead. A static-only/shared host can't
run the game service, which needs a long-running process with WebSockets.
Play locally (development)
Requirements: Node.js 22.12+ (24 LTS recommended) and npm.
npm install
npm run dev:server # game service on http://localhost:2567 (in-memory saves)
npm run dev:client # client on http://localhost:5173
Open http://localhost:5173 in two browser windows (or a second device on your network using
http://<your-ip>:5173/?realtime=http://<your-ip>:2567 — add that origin to ALLOWED_ORIGINS),
open a kitchen in one and join with the room code in the other.
To develop against PostgreSQL instead of the in-memory store:
export DATABASE_URL=postgres://user:pass@localhost:5432/afterhours
npm run migrate && npm run dev:server
How to play
- Flip the OPEN sign switch by the counter passage to start taking orders.
- Tickets show only the burger's name. Learn the builds — the recipe book (R, the touch
Recipes button, or the menu) has every recipe; Settings → Show recipe builds on tickets
turns on hints while you learn.
- Patties brown on the side touching the grill: flip them (spatula, or E/Use for a quick
flip). Cheese melts on a hot patty. Some burgers want grilled onions, others raw.
- Build on a tray from the bottom bun up, add exactly the sauces the recipe calls for, close it
with the top bun and put the tray on the pickup shelf under the heat lamp.
- More recipes unlock as the night goes on: 3 at first, 8 after a few minutes, then all 16.
Controls are in docs/CONTROLS.md.
Tests
npm test # rules, protocol, server room and store tests
TEST_DATABASE_URL=postgres://… npm test # also runs the store contract against PostgreSQL
npm run test:e2e # desktop + iPad-emulated browsers in one kitchen
npm run typecheck
Repository layout
| Path | Contents |
|---|
apps/client | Vite + Babylon.js client: menus, rendering, input (mouse/keyboard and touch), audio, networking |
apps/server | Colyseus room, authoritative kitchen simulation, HTTP routes, persistence, migrations runner |
packages/simulation | Engine-independent cooking, recipe scoring, stacking, interaction rules, shared Rapier physics |
packages/protocol | Replicated state schema, message validators, protocol version |
packages/data | Layout, items, recipes, prices, tuning |
database/migrations | PostgreSQL schema |
deploy/ | Dockerfile, Compose, Nginx example, environment template; deploy/windows Caddy and IIS configs |
assets/source | Blender (bpy) scripts that model, texture, light, bake and export all art; fonts |
scripts/ | Client build, backup, restore, smoke test, asset build, probe conversion; scripts/windows PowerShell equivalents |
tests/e2e | Playwright multi-browser tests |
docs/ | Plan, deployment, architecture, controls, recipes, assets, limitations |
Documentation
Licensed under the Apache License 2.0 (see LICENSE).
