Enforce player bans across matchmaking and sessions using the Epic Online Services Sanctions interface
domain: dev.epicgames.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Set up EOS Sanctions in the Developer Portal; if Anti-Cheat is enabled, cheat detections automatically generate sanctions
Choose the sanction action per offense: RESTRICT_GAME_ACCESS to auto-kick the player from Anti-Cheat-protected sessions, or RESTRICT_MATCHMAKING to block them from joining new sessions
Rely on the Sessions interface to enforce sanctions — EOS_Sessions_JoinSession refuses a RESTRICT_MATCHMAKING player and returns EOS_Sessions_PlayerSanctioned
Build a sanction-appeal flow if the title wants to let sanctioned players contest the action, per Epic's Sanctions guide
Feed player-submitted reports into sanction decisions rather than sanctioning purely on automated detections
Known gotchas
Sanctioned players can neither join nor register with a sanctioned session — the block happens automatically inside EOS_Sessions_JoinSession, so titles don't need to hand-roll the enforcement check themselves
Sanctions triggered by Anti-Cheat cheat detections are created automatically; sanctions for other trust-and-safety reasons must be applied manually through the Sanctions guide's flow
RESTRICT_GAME_ACCESS and RESTRICT_MATCHMAKING are distinct actions with different scope — picking the wrong one either fails to remove an already-connected cheater or blocks matchmaking without kicking them from an in-progress session
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?