{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
7/28/2016 3:46:11 AM
5
I can't go to the tower
This update is very bad y was kiked to the orbit every time, is only me or another one has this problem? Please Bungie fix it!
-
Hello, We have identified an issue causing players to receive BEAVER error codes at an increased rate. This issue was introduced in Destiny Update 2.3.1, and is causing complications regarding NAT settings. For more information and a potential workaround, please see our thread here: https://www.bungie.net/en/Forums/Post/209806134
-
1 ReplyHey, The latest patch implemented some error that has caused an increase in these glitches. Bungie is aware of the issue and is actively investigating. Stand by for updates. https://twitter.com/bungiehelp/status/758019356055867392 and https://www.bungie.net/en/Forums/Post/209860825?page=0&sort=0&showBanned=0&path=1 For more information and a potential workaround, please see the thread here: https://www.bungie.net/en/Forums/Post/209806134
-
3 RepliesBungie knows and is investigating the issue. They said... We continue to investigate issues causing an increase in BEAVER errors. To potentially reduce this issue, please see https://www.bungie.net/en/Forums/Post/209806134[/quote] For further information you can also view Cozmos reply down below [quote]It's us. Sorry if it wasn't made clear, but the issue with Beaver error codes was introduced in 2.3.1 and is definitely on our end. We offered up some advice on NAT tweaks as a way of possibly alleviating the issue while we work on a fix, but please don't interpret that as us passing the blame. Sorry for inconvenience, as soon as we have more info for you we will update this thread
-
I'm having the same issue. Can't go to any social spaces (Reef & Tower). Don't know why.
-
Edited by Jadaelbulvera: 7/28/2016 7:34:03 AMSame..48h straight..of constant kicks that sent me back to the tower..couple of posts on this forum erased as a form of ninja justice and an endless wait to see this thing fixed..usual stuff..they mess up.go live with a patch that was never tested..one meant to fix a tiny thing (which probably was generated in the previous patch) minor thing that wasn't fixed anyway but managing to screw and mess the usual stuff that used to work almost fine just because of divine intervention..so here we are..facing a beaver apocalypse..so after blaming us and our NAT and connections since the thing started happening they finally asked a moderator to walk around posts like yours and all the ones talking about this problem..to spread the words of Cozmo that finally admits they are the ones that screwed up..(as if we didn't know already) but be careful dear reader..it is a trap!!! The apology is as fake as a 3$ bill and the possible explanation is just smoke in the eyes..
