Box art - Destiny 2

Is Destiny 2 Izanagi’s Burden Quest bugged?

We bet you’re here because you’ve had issues with the Destiny 2 Izanagi’s Burden quest. Plenty of players just like you have had problems with the Mysterious Box and key mold parts, which means the quest is certainly bugged. However, Bungie is aware of the glitch and did state that a fix would be coming in the Festival of the Lost update that went live on October 29. So, is the Destiny 2 Izanagi’s Burden quest bugged? Read on to find out, Guardian.

What is the Destiny 2 Izanagi’s Burden Quest Bug?

Destiny 2 Izanagi's Burden Quest

For those who might be unaware, Izanagi’s Burden is a sniper rifle that you can earn from the Mysterious Box. In order to unlock the Mysterious Box, you need four keys. One of these is the Black Armory Key, but the quest to get Izanagi’s Burden is a long and complicated one. In summary, the Black Armory Key is the last one you get—or rather the one you should get, assuming the quest wasn’t bugged.

ALSO: How to get Destiny 2 Pluperfect Legendary Auto Rifle

Unfortunately, as soon as the latest fix was patched into the game, players once again began reporting that they couldn’t complete the quest due to a myriad of bugs attached to it. Specifically, players weren’t being given the key mold for the Black Armory Key.

The latest Destiny 2 update, known as the 2.6.1 patch, went live on October 29 and contained a patch for this bug. Despite this solution, however, players are still reporting that the quest is glitched.

Destiny 2 Izanagi’s Burden Quest Bug | Is there a fix?

Destiny 2 Izanagi's Burden Quest bug fix

Well, no. As we said, Bungie confirmed that a fix went out with the 2.6.1 update. Players are still having issues with unlocking the Mysterious Box or getting the key mold, though. Clearly, the problem is still there and needs to be sorted out.

You can let Bungie know about this continuing issue. You can lodge a complaint ticket on the Bungie Help website, or by contacting the development team on Twitter. Hopefully this issue will be resolved properly in next week’s patch.