Was raiding with a fireteam last night and I got DC'd with error code Beaver twice. Each time right before killing Golgoroth. First time, the team was cool enough to actually run it again, and right before Golgoroth was killed, I got DC'd again.
I re-connected and instead of runners by it through a third time, I just wanted to move on.
Ironically, I was on a different fireteam previously and two people kept getting disconnected with Beaver and Quail errors whenever they tried to join. One person would be able to connect, then got DC'd when the other person joined, and vice-versa.
What the hell did the MM update do? I have a feeling that the update is removing players from fireteams outside of PvP events and its screwing up the game.
-
Please search up beaver error code in bungie' website, or if you need further help please come back to me! Thanks!
-
Edited by SpunSour: 2/3/2016 11:10:07 PMyeah, I was running a strike solo with no problems at all, no slow loading screens but when I got to the boss two other players joined and I got booted and an unable to connect to destiny servers. All my problems started when IB started.
-
Was the same person host to both raids?