{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by dougcpa:
8/26/2021 7:15:04 PM
2
Bungie is currently investigating increases in Weasel errors.
https://www.bungie.net/en/Forums/Post/259485383?sort=0&page=0
[quote]We are currently investigating connection issues related to error codes ANTEATER and WEASEL.[/quote]
So your issue could be related to what Bungie is investigating.
Have you tried playing D2 on XBox to see if you get the same issues?
English
-
Sadly I don't have access to my Xbox at the moment. I only connected the account when Cross Save became an option in case I would switch to Xbox, but I haven't yet started it up on there. And I saw that post, but I didn't see anything related to beaver, so thought that this post might be helpful. Ideally a dev would see the "What I tried" section of my post and it might help them get to the root cause of the issue
-
Yeah, I was typing my reply and staring at your post and mis-typed Beaver when I should have typed Anteater. I've not heard of any increase in Beaver errors, but it is possible the cause behind Weasel might be kicking off Beaver.
