Is it possible to receive a clients violation/exit reason?

Hello,

We’re using EAC for a client/server game and have it mostly set up correctly. However, when we open a banned executable such as Cheat Engine on the client, the clients game will close and neither the client or the server will receive any information about why the client left the game. Is it possible to get this information?

The client is binding to EOS_AntiCheatClient_AddNotifyClientIntegrityViolated and the server is binding to EOS_AntiCheatServer_AddNotifyClientActionRequired. Neither of these callbacks are called before the client is forcefully closed.

Hello! This information isn’t exposed; with our anti-cheat tooling, this type of protection falls under the category of “prevention” and does not surface a notification through the SDK.

The other categorization of prevention is “detection”, which is where you would see Client/Server Actions and backend Reports/Sanctions.

That’s correct. These prevention measures are taken immediately to prevent tampering, sometimes even preventing the initial launch of your game.

Therefore, there is no window to handle any SDK notifications, and you also wouldn’t be able to rely on the integrity of the metrics/API calls.

Hi Ieuan.

Ok that makes sense, thanks for the info! We really just wanted to track this for telemetry reasons rather than directly applying any sanctions directly from this callback. I assume it’s recommended to just ignore this case and only track for any detection cases?