Bungie is aware of a Destiny 2 issue where players can’t respawn in Raids
Scott Duwe
In the newest iteration of Bungie’s weekly blog posts about Destiny 2 development, the company has laid out a number of known issues, including a particularly annoying one in Raid activities.
Bungie’s Raid test lead John Guesnier made a guest appearance in this week’s blog, talking about the complexities behind the issue and why it’s not a simple fix.
“The issue where players do not respawn in the ‘Leviathan’ raid is a memory issue due to the size and complexity of the activity, and it will require a code fix,” Guesnier said. “It is caused when a fireteam splits up across large distances while others remain back and swap out their gear. This has seemed to be occurring more often in recent weeks because we have updated our loot tables in order to make the ‘Leviathan’ raid a more rewarding experience, with more incentives to return to. We are still investigating a code fix for the problem.”
For now, a bandaid of sorts to fix the issue is to simply stick together as a team while switching around gear. It’s just a temporary solution, however, until Bungie can corral the bug.
“We realize that this is not an acceptable fix, but we wanted to give you info on how you can try to mitigate the issue while we work on it,” Guesnier said. “If you do happen to hit this issue even following those steps, then reequipping the armor set you had when you spawned into the activity may return your Guardian to action.”
The blog post also revealed changes coming to Iron Banner Control in update 1.1.4, to help make it feel more like the game mode from the original game in the series.
Bungie is also aware of issues with Mercury Heroic Adventures, Destination Emblem statistics, and Prestige Challenge Card score multipliers. Update 1.1.4 is targeted to contain fixes.
About the author
