Fulfilling your multiplayer game’s potential
summary
Shows how Unity Gaming Services and Multiplay get a struggling multiplayer project to “boring” launches by swapping bespoke backend work for proven components: self-service UGS, consumption billing, Multiplay orchestration, and server-authoritative multiplayer integration. Case study: Last Epoch moves from hobby devs to a 60–70 person studio with 500k Early Access buyers, 16 major releases and ~79 patches, uses relay and lobby for peer-first rollout, and reports steady scaling after partner integration.
AI-written summary · about
chapters (8)
- 0:00Multiplayer game success intro
- 3:20Scaling multiplayer challenges
- 7:54Unity services for living games
- 10:06Eleventh Hour Games' journey
- 18:03Multiplayer technical hurdles
- 20:27Unity simplifies multiplayer services
- 21:49Learn about Unity Gaming Services
- 22:12Q&A on funding and prototyping
related talks
49mMultiplayer Misadventures - Tales from making our first PvP multiplayer game in Unity
20mMultiplayer 101: Your Ideal Tech Stack
47mPanel: Mastering Multiplayer: The Super Session
52mPanel: Playing Together How To Boost Retention by Adding World-class Multiplayer Options
39mBehind the Game: Strategies for Building the Tech That Powers Today’s Top Titles.
24mMultiplayer Mastery: Key Considerations for a Successful Start
22mSuperstar Session: The Future is Cross Platform
21mWhen the Shit Hits the (RGB) Fan: What Can Go Wrong When Making Multiplayer Games