When the Shit Hits the (RGB) Fan: What Can Go Wrong When Making Multiplayer Games
summary
Lists the concrete failures to avoid: slow CI/CD and nightly builds with fortnightly QE, reinventing netcode instead of using vendors like net tension, parallabis, braincloud, and skipping cross‑play. Calls out mis-sized launch ops — picking three cloud regions for a global launch, underestimating CCU, and using spot instances that kick players. Recommends pay‑as‑you‑go, 24/7 support, rolling updates/multi‑versioning, realtime logs, and choosing a backend with fast deploys (1.7 seconds claimed) and wide regional coverage (250 regions) to cut latency and idle cost.
AI-written summary · about
chapters (5)
- 0:00Start
- 2:28Development Cycle
- 5:50Game Launch Crashes
- 12:06Matchmaking Needs To Be Flexible
- 18:10Closing Notes
related talks
24mMultiplayer Mastery: Key Considerations for a Successful Start
15mNo More BS: Demystifying Game Hosting Beyond Marketing Speak
39mBehind the Game: Strategies for Building the Tech That Powers Today’s Top Titles.
41mPanel: What Tools all Game Developers Should Have at Hand at all Times
47mPanel: Mastering Multiplayer: The Super Session
47mPanel: War Stories on the Business of Multiplayer Games
52mPanel: Playing Together How To Boost Retention by Adding World-class Multiplayer Options
31mTentpole Game Design: How to Make a Competitive Multiplayer Experience that Drives Deep Engagement