EAC, BattlEye, Riot Vanguard, and Proton compatibility

Scope

Anti-cheat compatibility is a property of a specific game build and service configuration. The middleware brand alone is insufficient evidence.

Do not use anti-cheat bypasses, unsigned kernel modules, modified clients, or security-disable instructions. They can compromise the system, violate terms, or trigger account sanctions.

Middleware boundaries

SystemProton capabilityRequired evidenceTypical blocker
Easy Anti-Cheat
Valve documents supported integration
Game developer enabled Linux/Proton module in shipped build
Module/depot not enabled or outdated
BattlEye
Valve documents supported integration
Per-title developer configuration and live service support
Title not opted in
Riot Vanguard
Riot-managed kernel security path
Riot-published OS/game support for exact title
Required kernel architecture unavailable
Custom anti-cheat
Unknown until title evidence exists
Developer statement plus current build test
Driver, service, policy, or attestation dependency

Why games fail

Wine can translate many user-space Windows APIs, but an anti-cheat may require a kernel driver, boot-time trust, attestation, signed services, or server-side allowlisting. Graphics success does not satisfy those security dependencies.

Evidence record

Record: game and App ID, live/beta branch, game build, anti-cheat product and SDK generation if known, developer statement, Valve badge/details, Proton version, device, test date, login, matchmaking, match completion, suspend/reconnect, and any error code.

Decision tree

No

Yes

No

Yes

Yes

No

Identify the exact game build and anti-cheat path

Current developer or Valve support statement?

Status remains unknown; do not infer from middleware brand

Linux or Proton module enabled in the shipped build?

Unsupported for this build

Test login, matchmaking, full match, and reconnect

All required stages pass without bypasses?

Record versions and test date as title-specific evidence

Record partial support or failure; use the official report path

Recheck after game or anti-cheat updates
  1. Check Valve's current device-specific compatibility details.
  2. Check the game developer's current Linux/Steam Deck statement.
  3. Confirm the live build still uses the same anti-cheat path.
  4. Test without bypasses or unexplained launch flags.
  5. Treat login-only or tutorial-only success as partial, not multiplayer support.
  6. Recheck after every major game or anti-cheat update.

Safe response to failure

Capture the visible error, game build, Proton log only when appropriate, and service status. Remove experimental flags, verify game files, and report through the game/Valve support path. Use a supported operating system for a required title when its security dependency has no SteamOS path.

Frequently asked questions

Does Proton support mean every EAC or BattlEye game works?
Does Proton support mean every EAC or BattlEye game works?
No. Valve documents middleware capability, but each title requires developer-side enablement and a compatible shipped build. Check the exact game, branch, build, and date.
Can a Proton launch flag bypass Vanguard?
Can a Proton launch flag bypass Vanguard?
No supported flag can replace a title's required kernel security architecture. Do not disable security controls, install bypasses, or risk an account ban to force compatibility.

Sources

Version history

  • 2026-07-15: Phase 5 title/build/date anti-cheat evidence guide and support-verification flowchart published.