A patchy line ruins a game night in a specific way: it is not that you cannot play, it is that you spend the evening saying “sorry, you cut out”. The fix is choosing games that do not care about latency, rather than hoping the wifi behaves.
What a bad connection actually breaks
Real-time games need a steady stream of small messages. Lose a few and the game either freezes or rubber-bands, and with two players there is nobody else to carry the round. Add a voice call competing for the same bandwidth and it gets worse.
Turn-based games send one message every few minutes. A dropout costs you nothing — the move arrives late and the game carries on.
Games that tolerate a weak signal
Turn-based, by design
Words With Friends 2 and Chess.com are the obvious answers. Nothing is timed to the second and the game state lives on the server.
Shared worlds with no live sync
Our Flower Garden and the farm sims only need a connection at the moment you act. If it drops, you reconnect and continue; nothing was happening in real time to miss.
Talking games
If the connection is bad enough that any game is a struggle, drop the game and keep the call. A question list needs nothing but one of you being able to read. Voice survives a far worse line than video, so turn the camera off before you give up on the evening.
What to stop attempting
- Anything competitive and real-time. Losing to lag is uniquely annoying.
- Large multiplayer lobbies — more players, more to go wrong.
- Anything with a per-second timer.
- Big first-time downloads on a call night. Install in advance, always.
Practical things that help
- Camera off, voice only. It frees up most of the bandwidth.
- Call on one device and play on another, so the game is not fighting the call in the same app.
- Agree a fallback before you start — “if this keeps dropping we switch to questions”.
- Download updates ahead of time rather than discovering one mid-evening.
Full setup guidance in how to run a long distance game night over a video call.
