Engineering Live Ops on Call of Duty: WWII
summary
Post-launch system design centers on remotely controllable settings and tiny hotfixes: mutable console variables are exposed as net overrides so movars can be toggled server-side (minor versions apply silently, major versions wait until a match ends). A content backend caches small CPC patches (aiming for weekly releases under ~10 MB) and supports dormant rollbacks and selective rollout to specific user IDs. Asset gates, branching (mainline/release/other) and automated playlists prevent spoilers and reduce package size, while analytics plus first‑party crash dumps drive targeted fixes.
AI-written summary · about
chapters (12)
- 0:00Start
- 5:42Net Overrides
- 6:09Versioning
- 7:49Login Queue
- 12:13Mark Files as Dormant
- 14:37How Do You Content Locke without Blocking Anyone
- 16:37Targeted Integrations
- 16:56Checking Approval
- 24:10First Party Crash Dumps
- 33:43Live Retail Kits
- 34:58Title Update
- 43:10Kill Switches
related talks
31mDesign & Implementation: Automated LiveOps Backend
47mWhat are the Challenges of Running Live Ops Across Different Game Genres?
38mLive Ops Disaster Stories: What We Learnt
27mDEVOPS DAYS MTL 2018 - Lenore Adam
23mKnow Your Players, Grow Your Game: A Guide to Live Ops in the Cloud
30mConfiguration Management Patterns
38mProgressive Delivery: Patterns & Benefits of Decoupling Deploy from Release
46mWorkflow on Fortnite