Bungie Answered
Steam Controller flagged by BattleEye Anti-Cheat
I just started playing Marathon with the new Steam Controller. 5 minutes into my first session of the day I suddenly receive error code: Plum
And get kicked back to the lobby.
Googling the error code seems to relate to BattleEye believing your input device is acting in a suspicious way.
The new Steam Controller does not use X-input or Direct Input, but rather relies on Steam itself in order it to work properly. I wouldn't be surprised if BattleEye mistakes this approach as suspicious.
Bungie, pls fix.
0
Comments
Hello there,
Thank you for reaching out to us.
We understand you are encountering error code Plum when playing Marathon with your Steam Controller. This does sound strange to us. While we realize you cite using the controller as the cause of this error code appearing, have you already verified if you stop encountering the error code when using a different controller, or mouse and keyboard?
If you have already tested whether you encounter Plum when using a different controller or mouse and keyboard, then please consider recording a short video which demonstrates you are able to replicate this. If you record such a video, you can upload it to a site like Imgur or Youtube, and link us to it here. We'll then investigate.
Thank you for the quick reply,
I was able to play a full match after restarting. If the error re-occurs I will update this post with evidence.
Hello again,
Thanks for the update.
We're glad to hear this issue you were experiencing with Plum has resolved. If the error code does recur and the circumstances which reproduce it are the same, then please let us know. We'll be happy to investigate.
Please sign in to leave a comment.