Live Ops Disaster Stories: What We Learnt
summary
Multiple Live Ops failures get pinned to concrete causes and fixes: a stress-tested launch lets only 10% of queued players through because connections and hardware aren’t scaled; a blockchain store sells tens of thousands of games during a sale leaving customers with €5 payouts instead of expected €30 so the platform refunds the difference; a last-minute feature ships without push notifications and gets almost zero engagement; a quick hacky patch breaks all locales when only 11 affected users triggered the original bug.
AI-written summary · about
chapters (5)
- 0:00Start
- 3:32What Does Liveops Mean to You
- 9:41What Is the Lesson Learned
- 24:50What Was the Actual Impact of the Initial Issue
- 34:34When Do You Think a Live Ops Game Should Come to an End
related talks
51mLessons from the Trenches: Live Ops Game Data Architecture
52mLet's Talk About LiveOps
50mDevOps Project Failures - Lessons Learned and Strategies for Recovery
15mWhy I Prefer Good Testing Over Excellent Testing
35mWhat is the 'gold standard' for live ops?
38mCompany culture - Influencing live operations
31mDesign & Implementation: Automated LiveOps Backend
22mWhat does live ops mean for your indie game?