Destiny 2’s long-awaited finale for 10 years of cosmic storytelling is finally here, and players spent the first day struggling to get through pivotal cutscenes without the servers crashing and booting them back into outer space . Bungie’s overnight fixes have fortunately brought some much needed stability to The Final Shape experience, but in the meantime fans are furiously taking inventory of important dialogue or emotional moments they might have missed. New Destiny 2 expansions are always mess.
Servers can’t handle the initial onslaught of players, weird error codes kick them offline, and new bugs materialize as all of the fresh content is explored for the first time outside of internal testing. The Final Shape has been no different, but the fact that it’s a cutscene-heavy conclusion to the loot shooter’s 10-year Light and Darkness saga has made all of these issues more annoying than usual. It would be one thing just to have trouble logging on or even just getting disconnected while on patrol.
But players are also missing entire scenes. The biggest culprit is an error code called “Currant,” which kicks players to space before important events unfold at the end of a mission, like the reunion with Nathan Fillion’s back-from-the-dead Cayde-6 for the first time in six years. Loving Final Shape so far BUT gutted about the currant disconnect error code stopping us from progressing the story though Hopefully Bungie fix this by the morning and we’ll carry on wit.
