{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
8/26/2016 3:44:14 PM
14
Weasel errors are getting very bad now.
Please Bungie,
Weasel errors are happening alot. I've tested alot on my side...all looking great hear, yet the weasel errors are still numerously happening. I've never been getting these errors, except on rare occasions. Check the forums, I'm very quiet, until now, because it is happening so often...need an explanation please, if it is work you guys are doing behind the scenes to get the new expansion ready, then please just say something. I've checked all over for server maintenance entries, but nothing. It is very disappointing to do year 2 stuff when you get booted out every 15 minutes or so. Enough said, need replies now. If amyone else, experiencing these please reply here also...to get voices heard as loud as can be!
-
ive been getting booted every 15-20 minutes or so
-
Here is the reason why. Alot of people are coming back to play destiny due to RoI being released in a few weeks. This is not unusual and happens evertime a new dlc is released. So its very clear what the issue is. There servers. Its been a problem from the start and will forever be an issue as they will never admit it is a problem on there end.... NEVER sadly. Only option we have is to put up with it or stop playing. For those getting #weasel and the #boar errors telling you you have no or damaged dlc the fix i have found is to delete all dlc and only install the expansion packs. Dont install any of the cosmetics or weapons (and lets be honest here who even uses them anymore lol) due to there major server issues when checking your dlc because you have so many around 8-9 it times out and gives you the boar error. Since doing this i have not had the #boar error but still continue to be kicked in the midldle of missions as most are. Happy gaming Guardians see you all at Felwinters Peak in a couple weeks...... hopefully 😂
-
I've been getting weasel and beetle error codes a lot lately.
-
I've been getting error coded for the past 3 hours my lord. My connection is fine, I green bar and magically it drops to red which never happens. I can't play anything man
-
Yeah the error codes are getting really bad
-
The errors on this game are so bad I've never been able to complete the final raid boss... this is ridiculous... I literally just went through the effort to configure my router and change the DHCP Server lease time to 10800, called the ISP got my IP changed from dynamic to static, made my xbox ip static, configured port forwarding. Still got the -blam!-ing error. This is not a client issue. It's a destiny issue and they need to fix it with rise of iron or i will never buy the sequel. I'm sick of it.
-
Same. This is getting ridiculous 😂
-
I know my connection is always green bar and then I get a weasel error for no apparent reason.
-
Im recently getting those errors too. It says my NAT type is 3, but it is absolutely not.
-
1 ReplyEdited by Admiral Porgus: 8/28/2016 3:26:55 AMLol I'm waiting on Bungie to post that this is all on our end and, of course as we all know, it's on their end.
-
unfortunately no matter how much i do with my ISP to confirm my connection is fine bungie will ALWAYS revert back to its all your fault and offer no explanation. whenever this happens i quit destiny untill bungie decides to get their servers in order. since destiny is the only one that claims anything is wrong.
-
watch how bungie says its a problem on your end.
-
1 ReplyI am weasel
-
I got error code: Chicken
