Enable the Anti-Cheat add-on in your EOS developer portal and ensure your EOS SDK version is 1.15 or higher
On the game client, initialize the EOS Anti-Cheat Client interface and call EOS_AntiCheatClient_BeginSession at session start, passing the local user's ProductUserId and the client mode EOS_ACCM_ClientServer
On the dedicated server, initialize the EOS Anti-Cheat Server interface and call EOS_AntiCheatServer_BeginSession; register each connected client via EOS_AntiCheatServer_RegisterClient
Relay integrity-check messages between server and clients using EOS_AntiCheatServer_SendMessageToClient and the corresponding EOS_AntiCheatClient_AddExternalIntegrityCatalog callbacks
Implement the Reports Interface to let players submit cheat reports, and handle EOS_AntiCheatServer_OnClientActionRequired to kick or ban detected cheaters
Known gotchas
The Anti-Cheat Server interface only applies to client-server (dedicated server) mode; peer-to-peer games use client-only mode which has different integration requirements
EAC requires start_protected_game.exe (from EOS SDK 1.16+) to be the launch wrapper on Windows; missing this causes EAC to block the game from starting
EOS Anti-Cheat runs backend detection updates silently; you must still handle EOS_AntiCheatServer_OnClientActionRequired callbacks on your server to act on detections
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp