Wardogs on Linux

It does not run. There is no native Linux build, and under Proton the anti-cheat blocks it. The developers have said Linux is on the pipeline but explicitly not an Early Access priority, and they say they are working on Proton — but the kernel-level Easy Anti-Cheat is what actually decides it, and today it says no. Below is our test, every dated developer statement with a link, and a straight list of what is still unanswered.

Native Linux buildNoSteam lists this game on Windows only.
In Early Access scopeNoStated by the developers, May 2026.
Proton support intendedYesReported August 2026. No date given.
Anti-cheatEasy Anti-CheatKernel level, per Steam's own disclosure.
Runs under ProtonBlockedTested 19 August 2026. EAC stops it.
Steam Deck ratingUnratedValve have not published a compatibility result.

Why the anti-cheat is the whole question

Steam's store page carries Valve's mandatory disclosure block for this game: Uses Kernel Level Anti-Cheat — Easy Anti-Cheat. EAC has shipped a Proton-compatible path for years, but it is not automatic — the developer has to switch it on for their title and ship the Linux runtime alongside the Windows build. A game with EAC and that switch off does not fail interestingly under Proton; it refuses to launch, or drops you at the menu and disconnects.

So "will it run on my machine" does not depend on your distro, your kernel or your GPU driver. It depends on one build-configuration choice at BULKHEAD, and they have never said publicly which way it is set — which is why the answer below is a test rather than a quote. EAC supporting Proton in general tells you nothing about whether it is on for this game, and the two are constantly confused.

Our own test

BlockedLaunched under Proton. Easy Anti-Cheat blocks it; the game does not get into a playable state.

Tested 19 August 2026 · measured · our own run, not a developer statement

This is the answer to the question the statements below do not address. It is also the weakest kind of evidence we publish: one machine, one attempt, on a pre-release build, and the Proton version, distribution, GPU and build id are not yet recorded — they render as unknown here for the same reason an unmeasured damage figure does. That is enough to say EAC refuses, because that is a switch at BULKHEAD's end rather than something a local setup talks it out of. It is not enough for you to reproduce, and we would rather say so than dress one run up as a compatibility report.

This can change without an announcement. Enabling the EAC Proton path is a configuration change, not a patch note — so treat this as true on 19 August 2026 and worth re-testing at Early Access launch. A stale “blocked” here would be the failure mode, and it is written into the source entry as a standing to-do.

What they have actually said

“I've been told, it's not a priority for the moment, BUT could slip it's way into our development roadmap once more pressing issues have been addressed. I'll be sure to communicate any developments to this when and if I get them!”
LossyBULKHEAD community manager13 February 2026confirmedsource
“Linux support is on the development pipeline, but not a priority for Early Access.”
LossyBULKHEAD community manager14 May 2026confirmedsource
“The developers behind the upcoming grand-scale FPS WARDOGS have confirmed they're working to support Proton so it's playable on Linux / SteamOS.”
GamingOnLinuxPress report13 August 2026reportedsource

The first two are first-party: a BULKHEAD community manager replying in the game's own Steam discussions. The third is a press report of a developer statement rather than the statement itself, so it is marked reported — it is the reason to expect Proton support at all, and it still carries no date and no commitment.

Steam Deck

Valve have not rated this game, so there is no Verified or Playable badge to report — unrated is not a bad rating, it is the absence of one, and a game cannot be rated before it ships. What can be said is the arithmetic below: the published minimum is a GTX 1660 or RX 590 at 1080p Low 60fps upscaled, and 100-player battles are the kind of load that hits the CPU hardest. Draw your own conclusion about a handheld; we are not going to invent a framerate for it.

Published requirements

Windows figures, read from the Steam store page. There are no published Linux requirements because there is no Linux build; these are what a Proton setup has to clear.

Read from the Steam store page. Windows only — the Linux and macOS requirement blocks on the store are empty, which is what an unsupported platform looks like rather than a low bar.
	Minimum	Recommended
OS	Windows 10	Windows 11
Processor	Intel Core i5 8600 / AMD Ryzen 5 3500	Intel Core i7 12700K / AMD Ryzen 7 5700X
Memory	16 GB	16 GB
Graphics	Nvidia GTX 1660 / Radeon RX 590	Nvidia RTX 3070 / AMD Radeon RX 6700 XT
Storage	50 GB	50 GB
Target	1080p Low @ 60fps (upscaled)	1440p Medium @ 70fps+ (native) or 4K Medium @ 60fps+ (upscaled)

What is still unknown

Any date for Proton support — "working on it" is the whole of the public statement.
Whether a native Linux build is planned at all, as opposed to Proton compatibility.
Whether the EAC Proton path gets switched on at Early Access launch, which would change the answer above overnight and without a patch note.
Whether any Proton version or launch option gets past it. One configuration was tried, not a matrix. If you have got further, tell us and it goes here with your method.
Steam Deck compatibility, which Valve rate after release.

If you are on Linux, do not pre-order expecting to play. As of 19 August 2026 it does not run, and nothing published commits to a date when it will. BULKHEAD themselves point at Steam's refund policy for the beta — the same policy is what protects you here, and it is a far better plan than reading a compatibility promise into "on the pipeline".

Check the Steam page

Last checked 19 August 2026. This page changes when BULKHEAD say something new or when a re-test says something different, not on a schedule — and either way the change will be dated here rather than quietly swapped in.