{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/18/2017 7:52:16 PM
4
Constant Cabbage Error ! Please help
I just bought D2, and i keep getting this "cabbage" error 1 minute into getting into the game (the area where everything's on fire). I tried uninstalling, reinstalling. My UPnP in enabled. I even enabled my DMZ, can't even connect to internet if i do that. I tried port forwarding, even thought i'm not sure if i did it correctly. I tried rebuilding database on PS4... still no luck. I have a "Luxul XWR-1750" router and my PS4 is connected through wifi. Please help, i'm just trying to play a game i spent $60 on. Thank you.
-
How much time do we have to wait, until you fix this "cabbage" for good? How do you explain that out of know where I'm starting getting this crap errors every day? Can you please bungie address this error more fast? And give us dalily update on you progress in this issue? Because like me other players are with no doubt, about to leaving Destiny. You did big mistakes in D1, and you are doing new ones "fatal ones". We buy the game and some of us not even can get through a simple campaign mission without getting kicked out. In my case, I started getting this error "cabbage" and "lettuce" 2 weeks back, since this week reset "lettuce" never happen again, but "cabbage" still haunted me, even after you last patch yesterday. We need a urgent fix for these errors!
-
I could only fix it by conecting my old modem. Hotspot worked ok before that but no perfect
-
Edited by ManatuBear: 10/19/2017 10:06:18 AMUse the wifi hotspot workaround, you should have more time between errors that way while you wait for Bungie to fix their netcode (in 6-12 months Bungie will have the problem solved...)
-
Welcome aboard. It seems Bungie is not able to solve this problem. This error (with a different name ofc) was present even during the open betas months and months ago. And, ovbiously, the cabbage error is plaguing a lot of users from day one.
