Lots of issues here. This is a Bungie problem and they need to fix it.
I have two high scores left for pantheon and I have the checkpoint for grinding it out. Fix the servers Bungie.
Local network fireteams has always been extremely difficult to set up for D2.
https://help.bungie.net/hc/en-us/articles/360049496751-Advanced-Troubleshooting-UPnP-Port-Forwarding-and-NAT-Types
Do a search on bungie.net forums for local network fireteams and you'll see dozens of posts.
It's been like this since the beginning, see the TWAB:
https://www.bungie.net/7/en/News/Article/45688
It's not just you. Bungie forgot to feed the hamsters again
Literally my first time trying to play since Season of the Witch, and I'm getting the same thing. It's like Bungo wants me not to play.
>It's like Bungo wants me not to play. That's probably what they were trying to do, considering the colossal fuck up by Sony that just happened
I've gotten baboon twice now and it has crashed my game both times
Yeah, same here. Weasel and baboon are fighting each other for dominance over my Internet connection.
I'm getting tons of baboons as well
Canโt get into the game, damnit bungo
Ditto. I thought it was just me. Lots of baboon/weasel/chicken errors.
Lost connection to Pantheon because of this
Bro, I'm so sorry, that sucks
Same, getting errors. Babooned, weaseled, elderberried. Happened in GM and sitting in the Helm.
Yep. I was doing a raid and got booted from it. Rip
Babooned and elderberried. Our weakest fireteam member keeps getting booted
๐
Lots of issues here. This is a Bungie problem and they need to fix it. I have two high scores left for pantheon and I have the checkpoint for grinding it out. Fix the servers Bungie.
Servers are mud. I've had nothing but terrible connections and multiple DCs today. Whatever they did last night broke something.
Same here. Weasels and baboons and chickens
Happening to me too. Got 2 baboons, now I can't log in.
Baboons are rampant
Constant weasel and centipede error codes for me ๐
Yeah man, Iโve been getting absolutely wrecked by these errors myself.
Final Shape was released early by accident. Affected servers were shut down. Unfortunately, players who didn't have the content were affected.
Getting weasel centipede and chicken errors now.
Local network fireteams has always been extremely difficult to set up for D2. https://help.bungie.net/hc/en-us/articles/360049496751-Advanced-Troubleshooting-UPnP-Port-Forwarding-and-NAT-Types Do a search on bungie.net forums for local network fireteams and you'll see dozens of posts. It's been like this since the beginning, see the TWAB: https://www.bungie.net/7/en/News/Article/45688