[b][u]BEAVER ERRORS UPDATE 7/29:[/u][/b]
Hot fix 2.3.1.1 has gone live on all platforms to reduce the BEAVER errors introduced in the 2.3.1 Patch.
Hot Fix Notes: https://www.bungie.net/en/News/Article/45015
Destiny Patch Notes and Status: https://www.bungie.net/en/Help/Article/13562
[b][u]Strike Specific Rewards: Nightfall Issue[/u][/b]
Destiny Player Support is aware of reports that players are not receiving strike specific loot upon defeating the final boss of this week’s Nightfall Strike. Nightfall Post Game Carnage Report Rewards are NOT impacted by this issue, nor is the Vanguard Heroic Strike Playlist. We have forwarded reports to the appropriate party for investigation, and will provide updates when available.
[b][u]Joining Fireteams in local networks[/u][/b]
This issue is now being tracking in a separate thread: [url=https://www.bungie.net/en/Forums/Post/210716770?sort=0&page=0]Marionberry, Canary, and Local Fireteam Issues[/url].
If you are experiencing this issue, please reply to the linked thread to make a report.
[quote][b][u]Increase in BEAVER Error Codes[/b][/u]
We have recently identified an issue causing players to receive BEAVER error codes at an increased rate.
[b]This issue was introduced in Destiny Update 2.3.1, and is causing complications regarding NAT settings.[/b]
• If a player has a Strict NAT, they may encounter BEAVER error codes when connecting to other players
• If a player with Moderate NAT is matchmaking into an activity where another player has a Strict/Moderate NAT, this can result in BEAVER error codes.
While we are continuing to investigate this issue, it can potentially be reduced by ensuring your personal NAT is [b]Open[/b].
For information on how to troubleshoot your NAT settings, please see this section of our [url=https://www.bungie.net/en/Support/Troubleshoot?oid=12915]Network Troubleshooting Guide[/url]:
https://www.bungie.net/en/Help/Troubleshoot?oid=13612
We greatly apologize for the inconvenience. We will update this thread when more information is available.
[/quote]
English
#Help
-
6 RepliesATTENTION BUNGIE SPIN DOCTORS! My NAT is open. Xbox One says it's open, my router says it's open, every other internet capable machine in my home says my NAT is as wide open as a 2 cent hooker. Yet, and here's what doesn't surprise me, Destiny says my NAT is strict every damn time I log on. Since the last update, not even this new "fix" spiking more beavers than a ladies night at a dive bar, I've been kicked from the game world repeatedly. Your response BUNGIE is that it's my connections fault and to follow your handy dandy guide to setting the optimal connection. I've done that and your game still tells me I'm set to strict NAT. But if everything else tells me it's open NAT, then maybe your side is actually at fault. Look at your network code please and for once stop BSing your player base. You aren't helpful, so stop drinking your own kool-aid. Thank you for your time