Following news that the release of the Destiny 1.2 update would be delayed for PlayStation and Xbox yesterday, some members of the games community and outlets like Game Informer began talk of the House of Wolves expansion being delayed as well. Bungie gave an update on the status of the update required for the expansion on Thursday and followed that with new bit of marketing that appears to show the developer is not worried about missing the planned Tuesday, May 19 launch.
Destiny Community Manager David “Deej” Dague provided slightly new news on the status of the 1.2 update via an update to yesterday’s forum post.
Here’s our daily update on our progress in delivering Update 1.2.0: https://t.co/YXwaet4JUS Stay tuned for more news on this front.
— Bungie (@Bungie) May 14, 2015
“Solutions for technical issues that have delayed the delivery of updates have been identified,” Dague wrote. “Work is ongoing and we’ll release the new content and the Patch Notes as soon as we can. Stand by for more information on timing.”
Bungie is essentially saying it knows how to fix what broke. The next step will be actually implementing the fix and testing to make sure that it doesn’t break anything else in Destiny in the process.
This thankfully doesn’t appear like it will delay the release of House of Wolves. The new Destiny trailer above featuring the expansion plus a reiteration of the May 19 release date was Tweeted out immediately after sharing the update on the status of the 1.2 patch.
— Destiny The Game (@DestinyTheGame) May 14, 2015
If the release of House of Wolves continues to go as planned, PlayStation and Xbox Destiny owners will receive the 18.104.22.168 update sometime after 1 p.m. ET / 10 a.m. PT on Tuesday, May 19. The team at Bungie is likely committed to work through the weekend if the current issues with the 1.2 update aren’t resolved by the end of business on Friday.
For those that aren’t aware, the Destiny 1.2 update has already been deployed to PlayStation and Xbox consoles. Bungie has not activated it yet though for this very reason. The developer wanted to ensure that the patch did not break anything before it went live.
[Image via Bungie]