At the Codex Hackathon in October, my team of three built Router Rumble: a co-op party game where the big screen shows a Wi-Fi network and every player's phone is both a controller and a device on that network. Routers overload and crash, and the team has to reroute traffic before network health hits zero.
My part: I handled most of the web interface, designed the device icons, and built the game's backend controls.
A party game gets played in a noisy room, on whatever phones people have, over Wi-Fi that might be bad. Joining has to be as quick as scanning a QR code, a phone that drops out can't ruin the round, and nothing is allowed to make everyone wait. That shaped most of the decisions below.
The big screen runs the whole simulation 10 times a second and draws at 60 frames per second. The Node.js server doesn't simulate anything: it only relays messages between the phones and the big screen in each room. That keeps it light. In a load test, 250 simulated players across 25 rooms each kept about 10 updates per second, using around 100 MB of memory.
Each player runs an access point, and their phone shows exact load numbers that the big screen doesn't. Nobody can play well alone, so people have to call out what they see. From the phone you can PUSH traffic to a neighbour, BOOST capacity for 5 seconds, FIX a crashed router, and from level 2 SEND a hungry device to another access point. Every tap gives feedback (points, streaks, and a buzz on real achievements), because on a touchscreen you can't feel whether a button did anything.
A room holds up to 10 players and a server up to 30 rooms. A phone that drops keeps its spot for 15 seconds, so a locked screen or a Wi-Fi hiccup doesn't kick anyone out. Inputs are rate-limited, so one person spamming buttons can't crash the server for everyone else.
With an OpenAI key, an optional "incident commander" comments on the game. It has a 3-second timeout, and without a key, or on any error, it falls back to written lines. The game never waits on the AI and runs fully offline. In a live demo, the only feature allowed to fail is one the game doesn't depend on.
Keep the server simple, give feedback for every tap, and treat every outside service as optional. Those choices are why the game still runs on a free hosting tier, and why you can try it yourself (the first load can take up to a minute while it wakes up).