Bungie solves a few bugs and offers a workaround

Oct 1, 2015 08:06 GMT  ·  By

Destiny developer Bungie confirms that all owners of the multiplayer shooter are now able to download hot fix update 2.0.0.5 for the popular game, and while it includes a few improvements in the patch, the Armsday Orders glitch is still present. As such, it recommends players not to redeem them from their inventory screen.

Destiny got its third expansion last month, in the form of The Taken King, and alongside it, developer Bungie launched a series of enhancements and updates for all owners of the multiplayer shooter. These patches not only laid the groundwork for the add-on but also fixed many different issues and stopped certain exploits.

A brand new hot fix solves some problems but still leaves issues

Now, Bungie confirms on its website that a brand new hot fix update is available for download for Destiny, taking the game to version 2.0.0.5 across the PS4, PS3, Xbox One, and Xbox 360.

As usual, the main goal of the hot fix is to solve a few problems but also stop a pesky exploit relating to the new Titan Sunbreaker sub-class, which got added in The Taken King. More specifically, a bug caused players to rapidly spam Hammer of Sol attacks. This is no longer the case, as the patch has resolved this exploit.

The update has also fixed an issue that didn't award players with loot when opening chests, as well as one that prevented them from earning their rightfully owed equipment from Valus Ta'aurc.

Armsday Orders are still bugged but there's a workaround

Unfortunately for fans, Bungie hasn't managed to resolve the Armsday Orders bug in Destiny. According to the studio, it's still investigating this problem.

As such, those who don't want to fall prey to the issue must avoid redeeming their orders from the character inventory screen. Instead, they must only get them from the Gunsmith's turn-in order window at the Tower zone.

This workaround is possible on all platforms, and hopefully, another hot fix update is coming as soon as possible in order to fix the underlying issue. Until then, check out the changelog for Destiny patch 2.0.0.5 below.

Show Changelog