I have followed the AntiCheat Interface docs and sample code to integrate it into our game in UE5.4. The anti-cheat callbacks and messages seem to be working correctly.
I am getting authentication failed errors during protected session for clients running without anti-cheat bootstrapper with the below log, which is expected behaviour.
LogEOSSDK: LogEOSAntiCheat: [AntiCheatServer] Queueing action to remove Client: 000001D5C5D660A0 ActionReason: 3 Details: Authentication timed out (1/2)
But for some clients running with anti-cheat bootstrapper are sometimes getting authentication failed error with below log which seem to be incorrectly failing.
LogEOSSDK: LogEOSAntiCheat: [AntiCheatServer] Queueing action to remove Client: 000001D5B4BD8B20 ActionReason: 3 Details: Authentication timed out (2/2)
Notice: the (1/2) and (2/2) in both the log.
I couldn’t find any more info on the authentication failing reason for such clients who are running anti-cheat bootstrapper. Other clients do not have any issue authenticating but happens only for some clients.
Please help me debug this. Thanks.
You can increase the logging level using EOS_Loggin_SetLogLevel.
The most common cause for AuthenticationFailed is the messages between client-server (or between clients in P2P) isn’t working correctly. Can you add some log messages to your code where the messages are sent and received to confirm the messages are exactly the same as our sender and receiver? We’ve had numerous partners run into issues because messages were being modified in their networking code.
Hi Seb,
Thanks for your quick response.
I’ve had to make several changes to the AntiCheat usage in our game. Finally, it looks like it’s working as expected. However, I sometimes get the Authentication timed out (2/2).
I have logs from a session where the Server registers the client and then they exchange a few messages and I can confirm they are being sent correctly over the network from the game’s end. But then the client stops getting callbacks from OnMessageToServerCallback (bound to EOS_AntiCheatClient_AddNotifyMessageToServer) and there’s nothing to send to Server. But the networked game just works fine and the client can play game fine (since we are not actually kicking them for debug purposes).
Here’s logs of host and client with VeryVerbose logging for LogEOSSDK.
Please help.
Glad this is mostly resolved. Could you share your ProductId? I’ll have a look at our backend. Thanks!
Sorry for the delay in responding. I’m not seeing any data on our backend. Could you send me the logs from the game start to when the error is returned? If you still have the previous logs, sending me the full file would be helpful. Thanks!
Yes of course! Sorry I should have mentioned you can create a private discussion to share them in my previous reply.
Sure, here’s our ProductId 704631b0c18b4c20985467ebce6f2729.
Looking forward to getting this resolved.
Thanks
Is it okay if I create a private discussion and share logs there?
Thank you very much for your persistent aid.
I’ve opened a private discussion and linked this discussion in the post. [Content removed]
We’ve added some logging on game side, and here’s client log for that.