Reports circulating on gaming forums say the multiplayer title For Honor will stop functioning on SteamOS and other Linux systems from mid-September, following an anti-cheat configuration change. Here is the mechanism behind that kind of block.
Key takeaways
- Anti-cheat software is the usual reason a Windows game that otherwise runs through compatibility layers suddenly stops working on Linux and SteamOS.
- Several major anti-cheat products ship Linux-compatible components, but activating them is a decision each publisher makes per title, and it can be reversed.
- Valve’s Steam Deck and the wider SteamOS ecosystem depend on the Proton compatibility layer, which translates Windows game code for Linux, and on publishers permitting anti-cheat to run inside it.
- A block of this type does not usually involve altering the game itself; it changes which client environments the anti-cheat service will accept.
- Claims about specific dates, titles or publisher intentions circulating on social platforms should be checked against the publisher’s own support channels before being treated as confirmed.
What is actually being described
The claim at the centre of this discussion is that an online multiplayer game will cease to launch, or will refuse to connect to matchmaking, on Linux-based systems including SteamOS from a stated date. Trendwire has not independently verified the date, the exact wording of any publisher statement, or whether the change applies to all game modes.
What can be explained is the mechanism such a change would use. Competitive online games generally run a second piece of software alongside the game client whose job is to detect tampering: memory editing, injected code, modified drivers or automation tools. That software is the anti-cheat. It is not part of the game’s rendering or gameplay code; it is a gatekeeper that reports to a server, and the server decides whether the player is allowed into a match.
When a publisher “blocks Linux”, they are typically not adding code that detects and rejects Linux. They are switching off, or declining to switch on, the anti-cheat vendor’s Linux-compatible module. Without that module, the anti-cheat service sees a client environment it cannot attest to, and refuses the session. The game may install and even reach a menu, but online play fails.
Why this is being discussed now
Attention tends to spike when a change is dated. A vague possibility generates little discussion; a specific cut-off date gives players a deadline, and deadlines travel well on aggregation sites and forums. That is the shape of the current conversation: a title that has been playable on Linux hardware is reported to be losing that status on a named day.
The broader reason it resonates is the growth of Linux gaming hardware. Handheld PCs running SteamOS have moved Linux gaming from a hobbyist configuration to a mainstream retail product. Players who bought such a device did so on the understanding that a large share of the Windows catalogue works on it. Each anti-cheat block removes a title from that share, and each one is read by the community as a signal about the platform’s long-term viability.
The background a newcomer needs
Linux cannot run Windows games natively. The bridge is a compatibility layer that translates Windows system calls and graphics instructions into their Linux equivalents in real time. Valve’s Proton is the best-known implementation, built on the longstanding Wine project. When it works, the game does not know it is running on Linux.
Anti-cheat is where the illusion breaks. Effective anti-cheat wants privileged visibility into the operating system — sometimes at kernel level — precisely because cheats hide there. A translation layer is, from the anti-cheat’s perspective, structurally similar to the tampering it exists to detect: an intermediary sitting between the game and the operating system, capable of intercepting anything.
The major anti-cheat vendors responded by building modes designed to work with Proton, allowing publishers to opt in. Opting in is a support decision as much as a technical one. It means accepting an environment the publisher’s team may not test, may not be able to reproduce bugs in, and cannot inspect as thoroughly. Some publishers enable it and leave it on. Others enable it, encounter problems, and withdraw it.
Who is affected and how
The directly affected group is small in absolute terms and vocal in proportion. It comprises owners of Linux handhelds and desktop Linux users who play a particular game. For them the outcome is binary: the game either works or it does not. There is no partial degradation to adapt to, and typically no workaround, because circumventing anti-cheat is itself a bannable action.
A second group is affected indirectly: prospective buyers of Linux gaming hardware. Compatibility ratings published for such devices are a purchase input. A title moving from “verified” to “unsupported” changes the calculation for anyone whose main game is on the affected list.
Publishers face their own trade-off. Supporting a small platform costs engineering and support time. If a publisher’s telemetry suggests a disproportionate share of detected cheating originates from clients it cannot fully attest to, the case for withdrawing support strengthens — although whether that is the reasoning in any particular instance is not something outside observers can confirm.
Where informed people disagree
The first disagreement is about whether compatibility layers genuinely make cheating easier. One view holds that a translation layer offers cheat developers a manipulable surface that kernel-level protection on Windows denies them. The opposing view is that the overwhelming majority of cheating occurs on Windows, that hardware-based cheats bypass software anti-cheat entirely regardless of operating system, and that the Linux user base is too small to represent a meaningful share of any cheating population.
The second is about proportionality. Critics argue that removing a functioning platform to address a small vector punishes paying customers for a problem they did not create. Defenders reply that a publisher is entitled to define its supported environments, and that promising support it cannot deliver is worse than declining it.
The third concerns precedent. Some read each block as evidence that competitive multiplayer on Linux will remain structurally fragile. Others point out that support decisions have been reversed before, and that platform growth changes the commercial arithmetic over time.
What this means in practice
For a player whose game is affected, the realistic options are limited. Dual-booting Windows on the same hardware restores compatibility at the cost of convenience and storage. Some players use a separate Windows machine or a streaming setup. Attempting to disguise the client environment is not advisable: anti-cheat systems treat evasion as a violation, and account bans are the normal consequence.
Refund eligibility is a common question and has no universal answer. Storefront refund policies generally rest on playtime and purchase date rather than on a subsequent compatibility change, though platform holders have discretion. Anyone in that position should consult the storefront’s own policy rather than rely on community summaries.
For those choosing hardware, the practical lesson is to check compatibility for specific titles at the point of purchase and to treat current status as provisional for any game with kernel-level anti-cheat.
What to watch next
The first thing to watch is official confirmation. Publisher support pages, in-game notices and storefront listings are authoritative in a way that forum posts are not. Where a change is real, it usually appears in those channels with a stated scope — whether it covers all modes, whether existing installations are affected, and whether it applies to related titles.
The second is whether the change is reversed. Anti-cheat support has been turned back on after community response in the past, and publishers occasionally revise decisions once support volumes turn out lower than projected.
The third is the aggregate trend. A single title moving to unsupported is a data point; a pattern across several publishers within a short window would indicate a shift in how the industry weighs compatibility-layer support. That pattern, rather than any individual announcement, is what determines whether competitive multiplayer remains broadly viable on Linux hardware.
Frequently asked questions
Why does anti-cheat software block Linux at all?
Anti-cheat generally does not target Linux specifically. It requires a verifiable view of the system it runs on, and compatibility layers such as Proton sit between the game and the operating system in a way the anti-cheat cannot fully attest to. Vendors offer modules that work within those layers, but each publisher chooses whether to enable them. If the module is not enabled, the client is rejected.
Can I bypass a Linux block to keep playing?
Attempting to disguise your operating system or otherwise circumvent anti-cheat is treated as a violation by most publishers and commonly results in an account ban. The supported routes are running the game on Windows, either by dual-booting the same machine or using a separate system, or streaming from a Windows PC. Neither restores native Linux play, and neither is guaranteed to work for every title.
Does this affect the whole Steam Deck catalogue?
No. A decision by one publisher applies to that publisher’s titles and, in most cases, only to specific games. The large majority of the Steam catalogue continues to work through Proton. Games affected by anti-cheat restrictions are a minority concentrated in competitive online genres. Compatibility ratings shown on the storefront are updated to reflect status changes, though not always immediately.
Is Proton at fault when a game stops working?
Proton is a compatibility layer, not a fault condition. A game that stops working because of anti-cheat is not failing due to a Proton bug; the anti-cheat service is declining to accept the session. Proton continues to run the game’s code correctly in most such cases, which is why players often see the game launch and reach a menu before online connection fails.
Can a decision like this be reversed?
Yes. Enabling anti-cheat support for compatibility layers is a configuration and support decision, not a permanent architectural change. Publishers have both enabled and disabled such support over time, sometimes in response to player feedback or after reassessing support costs. There is no guarantee of reversal in any particular case, and players should not plan purchases on the assumption that one will occur.
Where can I check whether a game works on SteamOS?
The storefront’s own compatibility rating is the primary source and reflects testing by the platform holder. Community-maintained compatibility databases often carry more detail, including recent user reports and workarounds, but they can lag behind or run ahead of official status. For games with kernel-level anti-cheat, the publisher’s support pages are the most reliable indication of current policy.
Sources and further reading
- Publisher support and community channels — the authoritative place for confirmation of compatibility changes and their scope.
- Valve’s Steam documentation on Proton and Steam Deck compatibility ratings — explains how titles are classified and tested.
- Anti-cheat vendor developer documentation — describes the modules available for compatibility layers and how publishers enable them.
- Community-maintained Linux gaming compatibility databases and gaming press coverage of anti-cheat policy — useful for tracking patterns across titles.
Surfaced from the reddit:Games signal “anti-cheat blocking Linux support”. AI-assisted draft, editorially reviewed.
