{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
5/23/2025 2:53:41 AM
2
Constant Bee and Bat errors
On PC, typically in Crucible, I'll receive disconnects that teleport me across the map as if I died or I'll get Bee errors that then error again to a Bat error. This has only been happening in this Episode since coming back.
I have confirmed UPnP is configured with my router. I have uninstalled and reinstalled Destiny 2. I have done the normal troubleshooting and my normal Internet activity is not affected. So please Bungie support staff, do not hit me with the "we're sorry" and networking troubleshooting guide link.
Alternatively, does anyone else experience this and have a local solution I could try?
-
I should report back that I figured this out, I think. I believe something from the "Killer Intelligence Center" in the "prioritization engine" was causing an issue. Something with my modem. I don't get it either, but I think it was doing something that BattlEye didn't like and it'd lag out my connection. It didn't accuse me of cheating, but the error mentioned it so that's the best I can come up with. I hope this sparks an idea in the future for possible help articles or if anyone has the same errors and some kind of packet prioritization engine.
-
1 ReplyHi there, Thanks for reaching out! Please try restarting the game and clearing the download cache: https://help.bungie.net/hc/en-us/articles/360049199051-Clearing-the-Console-Cache If you're on Steam, you can clear the cache by going to Steam>Settings>Downloads>Clear Download Cache. If you continue experiencing this after clearing the cache and trying both our Network Troubleshooting Guide and [url=https://help.bungie.net/hc/en-us/articles/360049496751-Advanced-Troubleshooting-UPnP-Port-Forwarding-and-NAT-Types]Advanced Troubleshooting Guide[/url], please consider reaching out to your Internet Service Provider for further troubleshooting.
