Home Artificial Intelligence The Division 2 Dev Says It Won’t Adjust Raid Difficulty on Consoles,...

The Division 2 Dev Says It Won’t Adjust Raid Difficulty on Consoles, Prompting Community Backlash – Push Square


Ever since The Division 2’s raid first dropped earlier this month, many console players in particular have been vocal with regards to the immense difficulty of the eight-player activity. At the time of writing, thousands of teams have completed the raid on PC — some of them in under an hour — while on consoles, barely a few hundred have found success.

As such, a lot of players have been calling for adjustments, but developer Massive Entertainment has come out and said that it won’t be touching the difficulty. Naturally, this has sparked a rather widespread backlash across various forums and social media. Even the ‘State of the Game’ livestreams are being bombarded with criticism on Twitch and destroyed by dislikes on YouTube.

Despite all this, community dev Chris Gansler made the studio’s stance pretty clear during the game’s latest developer livestream. “We’ve heard rumours about us changing the raid difficulty […] There’s currently no plans to change that. We know the raid is harder on console but we are happy with where we’re at,” Gansler said.

“We’re always open to changes. If the community is giving us the feedback that something is not how they like it, we’re not afraid to do changes. At the moment though, for the raid specifically, we aren’t planning any balance changes right now,” Gansler added.

However, the developer is looking into a specific artificial intelligence bug which can drastically alter the behaviour of enemies. Said bug could be lending itself to certain difficulty spikes, so maybe fixing that will have a positive impact on the balance of the game.

Still, it’s clear that the raid isn’t what a lot of players wanted at this point. Hopefully Massive can do something to get things back on track, because this is easily one of the biggest backlashes that the game has had to endure thus far.

This content was originally published here.