From fb6a280e854f37a9d00f0e850c3d934a903df036 Mon Sep 17 00:00:00 2001 From: Carlos Date: Thu, 4 Jun 2026 01:22:38 +0000 Subject: [PATCH] docs: update README to reflect 16 player limit Co-Authored-By: Claude Sonnet 4.6 --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 3a5127c..88616e2 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ Multiplayer network routing game built for team events. Players race to find the Each round, all players receive the same grid with a start node and a destination. Links between nodes carry modifiers (normal, slow, boost, or down). Players trace a route by tapping nodes on their mobile device and submit before the timer expires. Points are awarded based on whether the route is valid, how fast it was submitted, and how efficient the path was. -Designed for 2–4 players. Runs as a Docker container on `labmini-01`, proxied through Caddy with automatic SSL. +Designed for 2–16 players. Runs as a Docker container on `labmini-01`, proxied through Caddy with automatic SSL. --- @@ -252,11 +252,11 @@ Scores persist in Docker volume `route_rush_data` and survive container rebuilds - **`static/` directory must exist** — FastAPI's `StaticFiles` mount throws `RuntimeError` if the directory is missing, even if it's empty. Always create it: `mkdir -p /opt/route-rush/static`. - **No gzip on WebSocket proxies** — Caddy `encode gzip` breaks WebSocket upgrades. Omit it for any service with WS connections. - **Caddy stale bind mount** — after editing the Caddyfile, always use `--force-recreate caddy`, not just reload. -- **Player limit is 4** — enforced server-side. A 5th connection attempt returns an error. To raise the limit, change `len(game.players) >= 4` in `main.py` and update the lobby display in `host.html`. +- **Player limit is 16** — enforced server-side. A 17th connection attempt returns an error. To change the limit, update `len(game.players) >= 16` in `main.py` and the lobby display in `host.html`. - **PLAY AGAIN kicks all players** — by design. Host reset sends `kicked` to all connected players, clearing their session and returning them to the join screen. Players must re-enter their info for the next game. --- ## Scaling Notes -Current limit is 4 players. For larger groups (e.g. a full team event), the recommended approach is manual brackets: groups of 4 play simultaneously, winners advance to a final round. The host manages bracket progression manually between sessions. +Current limit is 16 players. For very large groups, the recommended approach is manual brackets: groups play simultaneously, winners advance to a final round. The host manages bracket progression manually between sessions.