Minecraft and Candy Crush leaders explain how live games earn the right to change

Leaders from Mojang and King say durable live games balance telemetry with qualitative feedback, protect familiar player expectations and treat operations as a long-term product capability.

Teams running Minecraft and Candy Crush describe longevity as a trust problem as much as a content problem. Players need meaningful reasons to return, but each change risks disrupting habits and expectations built over years. The operators therefore combine quantitative signals—telemetry, behavioral analytics and experiment results—with qualitative feedback from communities. Neither source is sufficient alone: metrics can show what changed, while conversations help explain why. Long-term teams also need technical and organizational systems that make regular change safe. Content pipelines, live operations, experimentation and cross-functional decision-making become permanent product capabilities rather than temporary launch support. The strategic tension is between familiarity and novelty. A mature game must remain recognizable to veteran players while making room for new audiences and changing platforms. That means evaluating updates against the identity of the game, not simply maximizing short-term engagement. The lesson for smaller studios is not to imitate the scale of Minecraft or Candy Crush. It is to design feedback loops, update capacity and community expectations before a game becomes dependent on them. Longevity is built through repeated credible decisions, not one large roadmap promise.