{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
12/22/2019 4:13:44 AM
6
Error Code Occurrences Are Spreading Through the Community Fast Right Now and It Might Get Worse Next Week
Normally with my group of friends that I play with on Destiny 2, it tends to be an inside joke when I get hit by error codes like CABBAGE or LETTUCE. No one else in this particular group tends to get hounded by as many error codes as I do. CURRANT happens here and there for all of us, mainly me but sometimes them too.
Throughout this week though, it's gotten bad. Now my friends who are normally not affected by some of these errors are getting them a lot, just like me. Reports have also gone up yet again. I think something about the event is still taking its toll on the servers and I'm worried about Iron Banner coming along as well next week. I think it's going to get bad.
The error codes that seem to be happening a lot with my group of friends include CURRANT, RABBIT and QUAIL. Normally for me, these errors are more rare than CABBAGE or LETTUCE, but I've seen them multiple times this week myself and my friends have been booted by them as well when they normally never see them.
The error codes that I'm surprised to see happening to a couple of other friends are CABBAGE and LETTUCE, because I've only met random players in the past that experienced these besides me.
The signs are pointing toward the servers. I know they use different ISPs and we're all experiencing similar things right now. And be ready for it to get worse because it will.
-
Same. Been getting currant and baboon errors. I've never had any issues with Destiny until this week, and everything else works fine on our home network. It started just having issues loading into the tower, but then I was kicked out of Sundial yesterday. Luckily, it put me back in.
-
Its been happening to me since last Thursday as well. I'm lucky to be able to play for half an hour without getting booted out by CABBAGE, BABOON or some other random code. I typically never encounter connection issues outside the rare one that just boots out my whole team at once, so this is just beyond annoying.
-
Same here. Would be nice if Bungie could acknowledge this issue.
-
My husband and I have been having the same issues. Starting this past week, we've been getting booted, a lot. I'd say (and this is no exaggeration) a 'minimum' of 20 to 30 times per day. We get reconnection notifications, load in, can see guardians but not enemies, and within a few minutes, we get the reconnection notification and loaded back in all over again. Rinse, repeat. We are both wired ethernet connections, on PS4, and have never had issues this severe previously. Sure, random, sporadic disconnects, but NOTHING like this. It's unplayable for anything more than patrols. But, even then, trying to get bounties done is difficult. We've done all the typical things you do when trying to figure out what's wrong and fix it, and have even called our internet provider to make sure the issue isn't somehow on our end. I'm already a little overwhelmed by the amount of stuff there is to do on a weekly basis (it's like a full time job trying to run one character, let alone three!), and this issue just makes me want to stop playing, which would really be a shame.
-
Yup same issue here, girlfriend and I play on the same network on ps4. Never had an issue until this week. Now its cabbage, lettuce and quail errors every 20 minutes. Was fortunate to get through the saint 14 mission without a boot but it has been miserable trying anything else. We have fios in case it matters.
-
2 RepliesYep, Tis the season.
