{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/6/2021 7:48:24 PM
11
Battleye still kicking players!
Batteye keeps timing out and kicking me. I'm either getting timed out or getting code plum. I am not cheating! I am getting false positives from battleye! I have reinstalled Destiny 2 twice, I reinstalled batteye countless times. I turned off/on my firewall. Allowed files through firewall. I don't know what else to do? Bungie please help!
-
ive gotten kicked bye battle eye 3 times all eror code plums not repeatedly kicked but its definitely going to be a problem and I hope I don't get banned by it when it starts auto banning people tomorrow
-
BUNGIE PLEASE FIX THIS
-
Same here. It's fustrating.
-
Yes tired of spending hours looking through fixes that don't work from battleye and no replies from bungie on this matter.
-
1 ReplyEdited by Syttz: 9/9/2021 4:31:46 PMGlad to see I'm not the only one... hopefully it gets fixed soon. UPDATE: I HAVE FOUND A FIX THAT WORKED FOR ME! First I verified the game files integrity. If you don't know how to do this follow these steps: Right click on the game in steam library > Properties > Local files > Verify game file integrity Once that was done, I backed the files up onto an external so that I didn't need to redownload the whole game. If you don't know where to find the files, then follow these steps: Right click on the game in steam library > Manage > Browse local files Once you're done backing the files up, delete the files in the above location and then copy your files from the external back into the exact same spot. Make sure that the files aren't saved in a file and that the files copy over exactly how they were before. This way steam will detect that the files already exist there and it will just install after a small wait time. After doing this I went back into the game files and you will see a folder that's labelled "battleye". Go into that folder and at the bottom you'll see two items, "Install_BattlEye" & "Uninstall_BattlEye". Click on unistall then follow the prompts to unistall, then click on install to reinstall it and follow all the prompts. This is just all the steps that I did to try and fix it and it seems to have worked for me. I hope this helps for you too!
-
SAME ISSUE HERE BUNGIE PLZ HELP US!
-
2 RepliesEdited by Azazael: 9/10/2021 3:19:54 AMUpdate: After a long painful search I found what worked for me. I updated ALL my drivers for windows, my GPU, anything that needed updated. Destiny 2 has been working fine since then. Update all drivers! EDIT: I was able to play for about 4 hours before the same bs started up again. All my drivers are fully updated and I'm still getting 'query timeout' or plum...
-
I thought I had "fixed" the problem after the first week of the new season by switching over to a hardwire cable which limits where I can play but I noticed I started contacting destiny 2 servers whenever people were around or for matchmade activities. It's frustrating that Bungie's only acknowledgement has been to say it has something to do with cheat software and then kick to to BattlEye. No cheat software ever used here and clearly there is no issues when playing solo so this must be something to do with Bungie's longstanding networking issues. Hopefully they'll acknowledge it or give us a fix.
-
Having the same problem, getting really frustrated they haven't said anything about this.
-
3 RepliesSame thing is happening to me. I can't play for 10 minutes without getting "Battle Eye Query Timeout" and error code "PLUM." I've messed with the firewall done just about everything I can find nothing is working for me. Commenting to stay on this thread.
-
2 RepliesFOUND A TEMP FIX, well.. It worked for me.. In Steam you'll need to run the game in Safe Mode, under Launch Options type in the box [u]-safe[/u] and then launch the game.. Normally after 5-10mins I get the Query Timeout from BattlEye and kicks me to either main menu or desktop. I've just gone nearly one hour in safe mode and still running, so might be a temporary fix possibly for some :)
