John Pilestedt, the former CEO and current Chief Creative Officer of Arrowhead Games Studio, the team of Helldivers 2explained that in his opinion developers don’t play enough to their own game, thus preventing them from having the right overview necessary to correctly evaluate player feedback and make the right decisions in terms of updates.
For those who missed the latest news, yesterday there was an important change at the top of Arrowhead Games Studio, with John Pilestedt who decided to leave the role of CEO of the studio to focus more on the future of Helldivers 2 as director creative. Shams Jojani, former Chief Business Development Officer of Paradox, will replace him. This change will therefore allow us to straighten out the situation and one of the objectives apparently is to ensure that developers have the time and way to “study” their own game.
“The first thing we need to do is make sure we give developers more time to play. It’s difficult to make the right decisions if your eyes aren’t on the road,” Pilestedt explained.
“Secondly, I want to make sure that we actively look at player opinion and create a holistic view of why certain types of feedback are given. And my theory is that the TTK is too high (acronym for “Time to kill”, or how long it takes on average to kill an enemy, ed.).”
Too many patches, in too little time? Arrowhead will reduce its publishing pace
As you may know, not all players are happy with the way the development team is supporting the game, with some complaining that the pace of publishing updates is too high and that the balance changes to weapons and stratagems are too drastic, preventing players from adapting to changes in the meta. It doesn’t help that in several cases the patches have corrected some problems, but also caused others, a sign that perhaps the pace of publication is so high that it doesn’t allow the developers the time needed to carry out all the necessary tests. .
The community manager Twinbeard also recently intervened on the issue, reporting that Arrowhead Games Studio intends to slow down the pace of patch publication, precisely to give developers the opportunity to optimize workflows and guarantee a higher quality standard, as well as that simplify the organization for the creation of new content.
