The recent Escalation of Freedom update causee backlash from the Helldivers 2 community due to key mechanics such as fire being altered, as well as various fire-based weapons being nerfed . Despite promises to improve these and revert many of the changes made, so far Arrowhead Game Studios hasn’t delivered this, although it has only been one week so we do have to have some patience. However, the studio released the 01.
000.004 update earlier this week and it has seemingly broken fire further, although this time it seems to be unintentional. U/Boatsntanks took to the Helldivers 2 sub-Reddit to detail their experience using the Flamethrower following the release of the 01.
001.004 update saying, “I find it hard to believe AH did it on purpose, but just not testing anything they do is bad enough. How can you get all this flak for nerfing the flamer, release yet another statement promising changes, and then nerf the poor thing again?” They then recount their experience with using the Flamethrower while facing a Charger in a mission, noting that it took much longer to kill than before the update.
“After today’s patch the Flamer will now barely hurt Chargers at all. I brought stun grenades, stunned it, and flamed it for the duration of the stun. I started with 3 grenades and it was still fine after that, so I kited and called in a resupply.
It was only after 10 stun grenades worth of flames directly did its butt explode. I’d estimate it took 3.5 tanks of fuel to do this, but of course, I was topped off when picking up new grenades.
” YouTuber Crazymrpipz tested out the Flamethrower following the 01.001.004 to see if it had been nerfed.
He discovered that it seems that some Charger’s hitboxes aren’t registering when using the Flamethrower, causing it to take much longer to take out. He did test the weapon against multiple Chargers and only experienced this issue a few times. So although this time it seems that Arrowhead didn’t nerf the fire, the broken hitbox is yet another issue that has been caused that the developers didn’t choose to fix before releasing the update.
.
