Here’s Destiny 2’s Latest Broken Damage Hack That Dodged QA

Posted by Paul Tassi, Senior Contributor | 6 hours ago | /gaming, /innovation, games, Gaming, Innovation, standard | Views: 13


Another day, another extremely broken bug in Destiny 2 that’s letting players instantly wipe out bosses thanks to the game’s anemic QA team that cannot catch all this stuff at this point. Maybe don’t fire most of them next time.

The bug in question is one of the easiest in the history of the game. You get a sword. You have no ammo for that sword. You jump. You light attack with that sword. Suddenly: INSANE DAMAGE!

How is this happening? I have no idea, the usual spaghetti code nonsense, I suppose. This joins the other big player-helping bug of the season, the fact that the newly buffed Sturm is buffing literally everything and allowing boss blow-ups as a result. Sturm hasn’t been disabled anywhere but Trials of Osiris at this point, but that may change soon. So what does Bungie do now, disable….swords?

All of this is ahead of the upcoming Epic Raid Race, where they’re doing that whole thing over again with a harder version of the raid with modified encounters and reskinned loot. Even raid racers are not terribly excited about that, and apparently even like the previous World’s First team is even going to bother with it. It seems likely that because there has been no Sturm fix, that it will be on the disabled list for the Epic Raid. Will they actually disable all swords for this as well, or can they squash this soon? Color me skeptical. The other option is just to leave all this stuff on and make it super silly because I mean, at this point, who cares? This isn’t really a real raid race anyway.

Bungie has previously said they were not going to be focused on “non-urgent” nerfs going forward as players have been annoyed with nitpicking rather than just buffing other stuff that needs it. But Sturm and swords seem like they probably qualify as urgent. Still, no updates. The sword thing was only found today or yesterday, I believe.

Destiny 2 is in one of the worst spots it’s ever been in the wake of the bafflingly bad Ash and Iron update. Bungie has emergency buffed some things on the PvE reward side of the game, but larger changes are taking some time. Some go live today. Others will not go live for months until Renegades gets here. I have personally been wondering that with all this going on, if Renegades itself might be delayed. We learned this past week that Bungie is still actively working on the exotic quest for this season. I’m not terribly hopefully that’s going to launch without bugs.

So, what will Bungie do now? Who knows, but they should probably figure it out quickly.

Follow me on Twitter, YouTube, and Instagram.

Pick up my sci-fi novels the Herokiller series and The Earthborn Trilogy.





Forbes

Leave a Reply

Your email address will not be published. Required fields are marked *