I've been researching this for the past 5 hours....exactly what I wanted to do with my Saturday night. It seems to me that a lot of people have posted about this and yet I see zero responses by Bungie. This is sad.
I play on pc (at least I'm attempting to play...) and this is the first time I've had this issue. I changed nothing. I started the game after purchasing two 30th anniversary bundles for my roommate and myself. After spending $200 my reward is to be disconnected repeatedly with an error caused by battle eye about a query timing out. In Destiny it says Plum.
Now I can understand bugs and stuff going wrong. It happens to the best. What I find absolutely unacceptable is that I have found posts on this dating back 6 months or more. Yet there is no fix. There is no official statement by Bungie. I'm sorry but the player base is not your staff. We should not be coming up with work around and possible fixes faster than you can.
If Bungie can't bother to acknowledge and fix something like this then why should anyone bother to play their game.
Get your -blam!- fixed.
PS. If a so called "mentor" comes in here telling me to contact Battle Eye support....so help me.... I have an idea, this is going to sound crazy, how about Bungie contact battle eye and figure out why so many players are having the same f'ing issue. Because it's not OUR job to fix the game for them. It is their job and they hired Battle Eye not us.
Take some accountability Bungie.
***EDIT***
I think I figured it out. I play the game through the Xbox app on pc. Which actually complicates the situation because Microsoft doesn't do anything simplistic. It downloads the game to your computer by placing it in a "Windows Apps" folder and accessing that folder requires you to give yourself administrator privileges to it (even if you're already an administrator). Then you can let the battle eye service through your firewall.....the next part I only figured out because I happened to be in task ma-blam!- right before the game crashed.
I have my hard drives set up so that a separate ssd is dedicated to just run the Windows operating system. Just in case I need to reinstall Windows for whatever reason. I then have an 1 terabyte NVME SSD where I install all my games and a 1 terabyte regular hard drive for standard files.
BattleEye not only installed itself in my game folder, which is where I found it initially. It also installed itself on my Windows SSD as a stand alone folder. I found this out by opening task ma-blam!- when my game froze, which it would do before popping the query timeout error, and noticing the location it was running from. It wasn't running from the game folder BattleEye....it was running from the stand alone folder which I didn't know existed.
I then went to Windows Defender and added that BattleEye to the allowed apps as well.
Ever since then I have had zero issues. I played 5 hours that night and 5 hours last night without a single problem.
Essentially everyone was correct it was the firewall. However, ensure you allow the third folder with BattleEye on your computer through or it doesn't work.
I really do not understand why when it asks you initially if you accept having BattleEye monitor your system during games it doesn't make all these changes automatically for you. Anyone who is less computer savvy will never figure this stuff out. It seems to me to be a failure on the programming side of things. I have multiple friends who work in the software field and every one of them said that there is no reason why BattleEye can't fix this other than it's not on their priority list.
Hopefully this helps someone else in the future!
-
Edited by ADragonWithin: 1/9/2022 12:45:00 PMCould 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.