Destiny 2’s new Honeydew error is preventing players from landing on planets


Destiny 2’s new Season of the Splicer is currently unplayable for some Guardians, due to a new error that players keep encountering: Honeydew. This issue is preventing many players from landing on any destinations.

After playing the season’s opening mission, we found ourselves unable to launch new destinations in Destiny 2. Other players have seemingly run into the same problem. Any destination in the game, including the ones needed to progress the seasonal story, force players into a “Honeydew” error whenever their ship starts to enter the loading animation.

Destiny 2 Honeydew error
The Honeydew error is keeping players from accessing the new Season of the Splicer content.
Image: Bungie

While we’re not entirely sure the scope of this bug, we’ve run into it ourselves, as have our friends, popular streamers, and some Redditors. Bungie Help, the studio’s tech-focused Twitter account, revealed plans to extend Destiny 2’s regularly scheduled maintenance by three hours due to the Honeydew error. Players can still play during this maintenance window, but they may run into additional errors.

However, Bungie Help is also investigating a separate issue where players can’t purchase season 14 (Season of the Splicer) on the season’s in-game page. It’s unclear if the two issues are related.

Bungie just launched Season of the Splicer earlier Tuesday morning, which includes a return to Destiny’s original Vault of Glass raid, a Transmog system, and some new activities.

Update: Cross-play is reportedly working between PC and Xbox players in Destiny 2 as of Tuesday’s update, further complicating the Honeydew errors. Bungie previously announced cross-play, but it’s not slated to appear until next season — season 15, which is scheduled to arrive this fall.

In the clip above, Twitch streamer JustManda joins a friend playing on a different platform — PC to Xbox. It’s currently unclear if this early addition of cross-play was intentional or a glitch. But given Destiny 2’s current instability, and the lack of any announcement from Bungie regarding cross-play in Season of the Splicer, it seems possible that the early addition of cross-play is partially responsible for the Honeydew errors.

Update 2 (3:45 p.m. EDT): Bungie has brought Destiny 2 offline to perform emergency maintenance. The Bungie Help account will update players on the game’s status going forward, and will reveal when Guardians can log back in.

It’s currently unclear if Bungie will need to roll back its Destiny 2 servers, something the studio has only done a handful of times. If Bungie does roll back the servers, players will lose all progress they’ve made since the Season of the Splicer patch on Tuesday morning.

Update 3 (4:48 p.m. EDT): Destiny 2 servers are back up.

While Bungie Help hasn’t yet tweeted that the game’s servers are now available and stable, multiple players — ourselves included — have been able to log in, land on planets, and progress the Season of the Splicer story.

There also hasn’t been a rollback, meaning players will keep any progress they made before the servers went down.

We haven’t had any server issues since logging back in, although players should expect a small queue when trying to log in to their Guardians.