Same, I'm also in Korea and it's non-stop currant, cabbage. Can't even load into destinations or tye tower at times. Solo ops, no enemies spawn then get kicked back to orbit with a currant error
English
-
I am also in the same predicament. I thought I was the only one. I’m in Korea receiving the same codes: coconut, cabbage, centipede and currant. No matter what mode I’m trying. I for one don’t complain about much in this game, but these connection issues are a little ridiculous, as I don’t play any other game lol.
-
Same, D2 is the knly consistent game I pkay but feels like everytimg they put out a new patch, something breaks and the last few releases were full of error codes. These last couple of days have been some of the worst and I've been in Korea for over 2 years now and it was never this bad. Got suspended from comp and kept running into solo ops activities that don't load properly so it boots me back to orbit with cabbage or currant
-
I think it's a bungie thing. They always say it's on our end but it's some communication loss between servers. Ever since they pushed updates it's just been error after another. It's luke the other regions getting the Tapir errors, and we're getting currant and cabbage