It always happens when I play with friends, I get cabbaged trying to launch any activity or planet. Sometimes I can't play the whole day, sometimes I can. It all started since the update from 2 weeks ago. I can't figure out what is causing the issue cuz I only have problems with d2.

Just to clarify, when it does let you into an activity or planet, does the error code ever trigger when hitting load zones like going from one public space to another (for example, from Archer's Line to the Hellmouth on the Moon)? If so, is there anything odd that you sometimes see before the error code happens? Like objects or enemies not loading in? I'm speaking from experience, but it could be different. Hopefully it's not the same thing.

Tryin to do hypernet for example, after killing the tormentor and going to the vex area, sometimes the enemies don’t spawn for the fireteam, then I get dcd and they spawn for my team but then I can’t reconnect.

I don't like the sound of that. That sounds a lot like what I had to deal with before the WorldServers had to be fixed years ago due to update issues. I never got direct confirmation that the WorldServer issue was causing CABBAGE errors back then, but if it wasn't, then it was a very odd coincidence that the errors stopped happening almost immediately after they fixed them. And not everyone experienced the issue either as it seemed to be constantly affecting the same people. While it wouldn't hurt to check with your internet service provider to see if there's anything going on with your connection or maybe see if you have some sort of firewall issue, I'm not fully sure what all you can do to stop the errors. The servers have been acting up lately, so it could be possible it's something on Bungie's end, but no one really knows what's going on right now. At most for right now, I can offer you some in-game workarounds for if you successfully manage to load into an area and you're about to traverse a load zone. They don't work every time or for every situation, and there's no guarantee that it will work for this particular case since I'm basing this off of an experience from over 4 years ago, but this helped me a little bit when I was dealing with it. 1. If you traverse a load zone but objects/enemies don't appear to be loading in the next area, quickly travel back through the load zone back to where you came from. In the past, doing this prevented the CABBAGE error from happening and you could attempt to go through the load zone again and see if it would work a second time. This might not work if the area you came from also starts to have loading issues. This is also best done for patrol zones as different player connections can affect how likely you encounter this issue and patrol zones can put you in different sessions each time you go through them. This is less likely to work while you are in a fireteam. 2. If you are playing with a fireteam you can talk to, before going through a load zone, ask and see if you can go through the load zone first. This is very dependent on the activity and the zones in particular, but this should help load things better if the zone session is started by you. There is a chance that the CABBAGE error can still happen, but as long as no one else enters the zone with you, you can try to backtrack to the previous zone like in the first tip. But if players have already entered the next zone, the chances of getting things to load right will probably plummet and you might consider that session to be dead in your case. Like I said, I'm basing this off of old news, so there's a chance that this doesn't help at all. But I'll keep an eye on the forums just in case. This issue has my attention considering what it did to me in the past.

May 5th Update: The problem is back but its worse now, I keep getting centipede error, which doesnt let me log into the game and when it does, i get rabbit and cabbage error code. Nothing has changed with my internet service, in fact D2 is the only game i have problems with.

Was your post edited? It's just now the 5th of May here. But still, that's strange to go for such a period of time without CABBAGE errors happening and then they come back with CENTIPEDE and RABBIT errors out of the blue. There's only been an update Tuesday at the weekly reset as far as I'm aware. But it appears as of a couple of days ago, some other reports have popped up for CENTIPEDE errors, which usually relate to just issues connecting to Bungie services. Could be a variety of reasons why players get that error. As for RABBIT, from my experience, it's not surprising that you're getting that error. RABBIT is very similar in behavior to CABBAGE errors. The only problem is that RABBIT usually starts happening while you're joining/loading into an activity from Orbit and by the time you notice that something's wrong, it kicks you to Orbit and that session will probably continue to kick you out. Other errors that you might encounter that behave similarly include LETTUCE, QUAIL, and CURRANT, though CURRANT isn't guaranteed to constantly kick you out of the same activity over and over. LETTUCE and QUAIL probably will though and I think those ones can happen when you hit load zones in the middle of an activity as well as loading in from Orbit. Here's a question though. What day did you see the errors come back this week? Was it fine earlier in the week AFTER the update Tuesday or did you not get on the game until later in the week?

It all started a week after into the light came out, after the update, I play everyday (unless I can’t cuz I get error codes sometimes)

Sorry, I misinterpreted. So you said that you were getting less error codes last week on your comment that I upvoted. But now the error codes have gotten worse again? When did it get worse again? That's what I meant. Did you notice it get worse immediately after the patch on April 30th? That's important to know. [quote]It all started a week after into the light came out, after the update, I play everyday (unless I can’t cuz I get error codes sometimes)[/quote] Also, this is good to mention as well. Into the Light wasn't originally planned and I imagine they put it together in a bit of a rush. If you weren't having issues before Into the Light, I could definitely believe that something happened on Bungie's end.

All the problems started when Into the Light dropped, before that I almost never had any problem with the game.

But do the error codes get better or worse after specific patches? We've had multiple patches since Into the Light dropped. That's what we need to know. If it seems to be getting better or worse regardless of exactly when the patches happen, then that makes this much more complicated and harder to figure out. I can explain it clearer if you still don't understand.

The first update I got just a few errors but I was able to play shortly after, the second week I got flooded with cabbage errors, it kinda fixed itself after a few days. The last week I was not able to even log into the game all day, it all fixed itself the next day. It’s very odd and I dont understand at all what’s happening.