With the release ofDestiny 2: The Finale Shape, the servers have understandably been overloaded causing a bunch of new error messages including the Plum error. Associated with the BattlEye anti-cheat protection, here is how to fix theDestiny 2Plum error when it occurs.
Destiny 2Plum error fix
In a nutshell, theDestiny 2Plum error is triggered by an issue that has occurred with BattlEye, the anti-cheat the online FPS uses to prevent cheaters. The error itself my even indicate that BattlEye has detected a problem with your computer, possibly in relation to having a “cheat” folder open on your computer. While this error can certainly occur if it detects some sort of cheating software on your machine, with the launch of the new expansion, this is actually a networking issue.
TheDestiny 2Plum error occurs because when BattlEye attempts to validate your machine with theDestiny 2servers, it’s timing out due to the servers being overloaded. Because this isn’t normally an issue, it’s triggering the Plum error when otherwise it would go through without issue.
If the Plum error is in fact being caused by overloaded servers, you simply have to wait until the issue is alleviated and you are able to connect with the issues with no problem. This typically happens within a few hours or the day following the release of a new expansion or DLC. However, if the servers appear to be stabilized and you’re still getting the error, here is how you’re able to fix theDestiny 2Plum error:
