Never had any problems associated with these error codes, and now I can't even load into a destination or start a mission with out being kicked to orbit.
-
Hi there, Thanks for reaching out! We're aware of the server errors and are investigating currently.
-
Edited by Facilus: 6/8/2024 11:34:10 PMgot the Cabbage error in the last part of the mission to find Ikora, checked my internet connection and it's all right on my end, sheesh, was trying to finish the campaing today but seems that won't be possible
-
Gotta love how the advice on Bungle's troubleshooting pages for various errors usually boils down to, "Hey, don't look at us; it's probably your fault."
-
Team Currant for the win, it seems.
-
1 Replyabout 5 currant error codes to load into a destination, then another currant kicking me to orbit when I try to start the mission, and if by some miracle I actually get into the mission I then get a currant error as soon as the mission ends, making me miss any and all end of mission cut-scenes, and that last one is the biggest problem for me. Culmination of a 10 year story and I have to get the story beats from YouTube because I got kicked to orbit for an error. This sucks
-
Team Weasol checking in. I was halfway into the first mission & bam, error coded to bed.
-
2 RepliesThis screams server integrity issues to me. I haven't had CABBAGE since Shadowkeep and the character corruption issue back then with the World Servers. I can't even start the first mission because of CABBAGE right now.
-
Yep. Impossible to play a game which many have spent over $1k through the years. Well, we’ve waited many months more than originally scheduled. Apparently there were literal roach casino resorts in the version originally set to release. This is the worst iteration of a content drop I have ever witnessed. Shame on you all. I can’t really comment on the game or campaign because II CANT PLAY IT. Stupidly stupendously annoying. Way to garner goodwill amongst players there Bungie. Solid business type stuff 👌
-
I keep getting the same error message and boot it back to orbit and I have a good connection too here at home
-
42 RepliesWhile I understand everyone paid money for this DLC and everyone was excited to play it through and see the end of this 10 year story; but y'all absolutely CANNOT be so dense to think that servers won't have problems with thousands of people playing on them at the sametime? Come on. That's silly to think that won't happen. It's happened with every Destiny DLC, and yet here you are, once again complaining about the same things have happened with the previous DLC's and any other DLC from a game. There is so much love and time put into these things for you, the consumer, to absolutely destroy in 2 seconds because "it doesn't work right as soon as it launches". Like I said, i get it, you want to play the game, but they obviously wouldn't just release the DLC and say "Lol okay going home now" They're actively working on a fix, so just give it some time before jumping down their throats about how shitty their game is. YOU STILL BOUGHT IT, AND YOU'RE STILL GOING TO PLAY IT. So....
-
2 RepliesWho knew the final shape was a Current...smh? This is the end for you bungie...you know that right?
-
Same. I am unable to go to any planet or social location other than the tower now.
-
5 RepliesEdited by Max Data: 6/5/2024 1:01:58 AMfinished the 1st mission on legendary, after the boss fight was immediately sent to orbit, no cutscene - nothing. i had BETTER be able to get the cutscene if i go back and do it on normal (once i can launch literally anything in the pale heart without getting an immediate currant)!! this is just a travesty for the story. i'm not redoing this stuff on legendary any time soon, and the way things are right now these are barely - if at all - connected, discrete missions. i can't believe they are letting people play it this way, just take the thing offline until this stuff is fixed. edit: i was finally able to launch it on normal after ~13 tries (every one a currant). speedran it by passing by every enemy except the ones required to open gates. after the boss, black screen - currant - orbit. i alt-f4'd. bungie this is insane, you have got to either sort this out or turn the damn thing off.
-
Imagine how that'd work out for anyone else in the world... you have one job for 10 years and everytime you do it you fail this hard..
-
So many of us getting the same code currant. I have tried trouble shooting and nothing has fixed the issue. Bottom line, servers seem to be overloaded with players trying to play the new dlc. Ive been waiting for this since i bought it back in September, and now i have to wait a bit longer for bungie to fix their stuff. You would think they would have learned their lessons by now since thiss has been an on going issue with new dlc since destiny 1. Hope marathon doesn't have these issues as much. lol
-
Currant code for dungeons and campaign.
-
2 RepliesYup. I can't go anywhere, and I can't even start the campaign because of currant. I've tried restarting my computer, my router, the game...everything. My partner is on the same Internet and was able to play after I got kicked for the fourth time. Same exact computers, same specs... So no idea but it's extremely frustrating.
-
2 RepliesEdited by Dillinger: 6/5/2024 1:23:25 AM+1 I too am experiencing this issue. I decided to log out and hop back in the queue since I couldn't do anything else. Unfortunately, because we can not launch story missions from the Director, I found that I was blocked from progressing since any attempt to land at the first destination public zone invariably results in a CURRANT or CACAO error. I had tried about 30 times in a row, and I figured that was sufficient. * Even after passing through queue, I find my experience plagued with ATTENTION pop-ups, indicating connection issues, and then- again- a CACAO or CURRANT error every single attempt to land at the destination spot. ** It seems like the game will permit a landing and play if the zone I'm attempting to land in has an available, empty instance. In that case, I can land just fine (e.g. the EDZ patrol zone) and do things in the local area. But, if I attempt to head into another area I am presented with an infinite load screen (or long enough that I tried fast traveling instead and was booted with a CURRANT error). While in the local area nobody else loads in either - it remains a solo instance but otherwise functions normally.
-
I have been trying for the last 7 hours. Same thing every single time: Currant. I can land anywhere else and be fine, but as soon as I try anything Pale Heart related it's an instant error code. I'm at an all-time frustration and truly at a loss for words. Whatever hype I had when I started the game has literally been squashed pretty much flat.
-
I don't wanna play pvp. But I wanna play. So I'm playing pvp.
-
You could try a VPN to another country that is not so busy as America Maybe Middle East or somewhere with less player population Heard this works fir many of errors in Destiny
-
Edited by Prolific-Jay: 6/5/2024 1:56:19 AMNonstop currant errors here too. I was able to fly into the pale heart once, hit the mission flag and then got curranted back to orbit lmao. This is ridiculous
-
3 RepliesTrying my hardest not go on a rant lmao… 10 years in, and this is the state of the game. Same here—constant currant error codes. I can’t even start up the mission.
-
I am having the exact same issue. Able to load into most places, except the Pale Heart. PvP and Gambit are playable, along with the strikes playlist. Just having issues loading into the Pale Heart. I completed the first three missions, is the fourth bugged?
-
1 ReplyBungie likes to word it as if it's the clients fault the game crashed. 'check YOUR settings'.. It's never my settings, not in 10 years has it been my settings.. Bungie always looking to off load the Q/A issues to the user.
-
I give up. Currant wins. Who knew the Final Shape was a stupid berry?