{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by ADragonWithin:
1/9/2022 12:45:00 PM
1
Could you please clearly and accurately describe exactly how you suggest Bungie is supposed to fix an issue or discuss it with BattleEye support when: a majority of players don't have the issue, the issue doesn't happen during testing, the issue is caused by BattleEye and not the Desitny 2 game, and the issue is known to occur in other games, not just Destiny 2?
As the issue IS a BattleEye issue itself, caused by BattleEye choosing to disconnect you from the gameworld because BE cannot contact its own servers, and you, specifically, are having the issue, then you, specifically, are the one that need to contact BattleEye Support concerning possible fixes.
Yes, there are posts dating back a while, because random people have also had the issue due to the uncountable differences in hardware, networking, and software that can happen on PC. Because it's unique to each person who has the issue, there is no support that Bungie can offer you to fix the issue for you. The issue is not caused by Destiny 2; it's caused by BattleEye, and as such, it's outside the range of what Bungie can assist with. The error code Plum does not cause the BattleEye Query Timeout, the BattleEye Query Timeout is what leads to the Plum error, as it's what was programmed into Destiny 2 as a catch for that issue being thrown.
I know you don't want to hear "a so called 'mentor'" come in here telling you to contact BE support, but, unfortunately, that's the only answer you'll be able to receive, since the issue is caused by a problem between your setup and the BE service.
Have you tried the multitude of fixes that can be found by simply searching the internet? Yes, there ARE some people that have fixed their own personal version of the issue; your issue may be caused by the same thing that caused one of them, so if you're lucky, one of their fixes may alleviate the issue for you.
I am not trying to defend Bungie's involvement with the error; they did choose to go with BE to help alleviate the problem with cheaters on PC. Unfortuantely, third-party hiccups happen sometimes when a company does so. But, sadly, there's just nothing Bungie (or we) can do to help you with your specific version of the issue. I know it can be frustrating to be told that you have to check it out on your own. There's just literally nothing we can do to assist you, as the issue isn't on this end of things. I'm trying to help alleviate some of your frustration, though I also know my post will probably add to it because it's not the answer you want to hear; unfortunately, not wanting to hear an answer doesn't change the fact that it's the answer.
English
-
Edited by Pinkcookymnstr: 1/9/2022 5:41:39 PMI have tried every single thing I have found online to fix this short of reinstalling windows. Battle Eye doesn't even address this in their error section. Which means I would have to contact them directly somehow. I know it's not Destiny itself causing the issue. However, Battle Eymye was integrated into the game at Bungie's behest. I support the steps to prevent cheating. What I don't support is how there is no clear guidance as to what to do to fix this issue. Whether on Bungie's side or Battle Eye. So essentially I'm left to stumble around beating my face against a wall until it magically fixes itself. Something is causing the query timeout. Either Bungie or Battle Eye should be able to state what that cause is. Then at least people would have a direction to troubleshoot. As it is I'm seeing, "there is something with your pc making Battle Eye timeout....good luck!". So it is a wee bit frustrating to say the least. I guess when it comes down to it Bungie could at least contact Battle Eye and inquire about the issue and maybe that would get Battle Eye to address this. Because I'll tell you this much having some people that do not directly effect how you get paid poking for answers is not quite as effective.
