Arc Raiders launch leaves devs super unhappy and tired
On the surface, Arc Raiders has been a roaring success for a live-service game. It launched to massive numbers, sustained strong community engagement, and maintained a steady stream of updates and patches. But behind the success story, the leadership is now getting candid about the human cost of that sustained momentum.
Aleksander Grøndal, executive producer on the project, reflects on the immense pressure this transition brought. “Transitioning to live-service is going to be fucking hard,” he admits. He notes that while he had mentally prepared for the difficulty, the reality of the workload proved far more challenging.
The demands of managing a massive live-service operation place an extraordinary toll on the development team. The staff has been worn down by the necessity of constantly answering to millions of players on an ongoing basis. Grøndal acknowledged that the team was putting out content as fast as possible, but often felt that this pace wasn’t necessarily interesting enough, and they were constantly struggling to meet the demands.
This push for constant updates meant the team was frequently overshooting their capacity. Beyond adding new content, the effort required constant firefighting—implementing bug fixes, addressing exploits, and managing other constraints—making planning incredibly difficult.
The pressure wasn’t just internal; it bled into player dissatisfaction as well. Grøndal shared a personal history, drawing from his experience at Electronic Arts, where he personally faced severe burnout. He recalls having to take a five-month break and sick leave after pushing too hard on a project, realizing just how critical it was to protect people.
This experience underscored a crucial lesson for the entire team: the need for a framework that allows for creativity while ensuring a healthy work-life balance. Grøndal emphasizes that creating systems that support the creative process, rather than constantly pushing against limitations, is essential for sustainable development.
As a result, the development cadence has naturally shifted. While the team remains committed, they have since aimed for slower, more deliberate rollouts of new features, prioritizing quality and sustainability over relentless speed.
Buy on Amazon
Credit
