Agenda
Content Updates Without Maintenance: A 'Clash Royale' Live Ops Case Study
WOOKJIN LEE (Senior Server Developer, Supercell)
Pass Type:
Academic Pass, Festival Pass, Game Changer Pass, Indie Pass, Start-Up Pass
Track:
Production & Team Leadership, Programming
Audience Level:
All
Format:
Lecture
Vault Recording: TBD
Audience Level: All
For live games, maintenance is sometimes necessary. But what happens when a team has to stop servers for one number?
In this session, Wook-Jin Lee from Supercell shares a Clash Royale case study on Dynamic Data Change, a capability built to ship certain content updates without server maintenance. He walks through the original cost of release due to maintenance, why it was so difficult to implement such a system in the first place, the pivot from A/B testing infrastructure to a live-ops content update pipeline, and a real incident that exposed gaps in validation and rollout safety.
This is a practical talk about changing release infrastructure in a mature live game: reducing unnecessary player disruption, learning from failure, and finally having a low-cost content update pipeline.
In this session, Wook-Jin Lee from Supercell shares a Clash Royale case study on Dynamic Data Change, a capability built to ship certain content updates without server maintenance. He walks through the original cost of release due to maintenance, why it was so difficult to implement such a system in the first place, the pivot from A/B testing infrastructure to a live-ops content update pipeline, and a real incident that exposed gaps in validation and rollout safety.
This is a practical talk about changing release infrastructure in a mature live game: reducing unnecessary player disruption, learning from failure, and finally having a low-cost content update pipeline.
Takeaway
Attendees will learn how one mature live game challenges themselves to reduce maintenance dependency, including practical lessons on rollout safety, validation gaps, incident recovery, deployment frequency, and how to decide whether to continue after a live feature breaks.
Intended Audience
This session is for engineers, producers, live-ops teams, and game leads working on mature live games. Experience with release pipelines, backend systems, content operations, or live-service development will help, but no specialist knowledge of Clash Royale or server architecture is required.