You can sign up to get a daily email of our articles, see the Mailing List page.
We do often include affiliate links to earn us some pennies. See more here.

Easy Anti-Cheat not as simple as expected for Proton and Steam Deck

By - | Views: 78,371

Even though Epic Games announced recently how they expanded support for Easy Anti-Cheat to have full support of native Linux, plus Wine / Proton (and so the Steam Deck), it seems it's not as easy as we hoped.

In the original announcement, Epic mentioned how it can be enabled with "a few clicks in the Epic Online Services Developer Portal" but the situation is never that simple. A developer of Warhammer: Vermintide 2 has written a post on Steam to explain, noting that there are two versions of EAC. There's the original and the newer version used via Epic Online Services. The majority of games are likely still with the old version, since the newer one needs SDK upgrades and newer integrations.

We already knew that developers needed the latest SDK from the original announcement, but this makes it simpler for us all to understand.

Here's what they said:

So we have looked in to this. It's far more complex than first suspected -- EAC has two versions. Non-EOS and EOS (Epic Online Services). Most games historically use Non-EOS EAC. It's the one Vermintide 2 uses as well. Epic only added Proton support for the EOS version of EAC. Therefor in order to implement proton support for Vermintide 2, a huge amount of reworking of the EAC implementation would be required, which may also require all players to authenticate with Epic Online Services as well -- perhaps even logging in to the Epic environment (to be confirmed, however).

So the "just a few clicks" statement made in the original announcement wasn't entirely accurate, and would only apply to titles using the EOS version of EAC, which simply hasn't been many games aside from either pretty new ones, and likely predominantly Epic exclusive titles.

We are still looking at what is or isn't going to be possible, but it's not as easy as it was made out to be -- far from it in fact.

There may be other solutions or workarounds, but ripping out the old EAC and rewriting everything to implement "NuEAC" and potentially asking our entire playerbase to connect through and sign through EOS for an honestly tiny market share that was (and would remain) unsupported from the get go might be a deal breaker.

Time will tell.

One part we already know not to be true, is a requirement of Epic Online Services authentication, as the developers of Brawlhalla showed in their own testing with the new integration which worked without users touching Epic's services directly.  The other point remains though, as developers won't upgrade from the older implementation to the newer without a good reason, due to extra work involved when the older one is still getting the latest EAC updates as normal (as confirmed in a later post). Although, there may come a time Epic force EOS for it, but it stands to reason they haven't currently as it would have been a big upheaval for so many developers using it and likely caused plenty of developer backlash there.

Tripwire Interactive also hinted towards the exact same thing, when asked about hooking up support for
Rising Storm 2: Vietnam, a developer noted back in September 2021, "The version of EAC used on RS 2 is not the version that is advertised in this, and it is not something that will work for RS 2 players.".

Hopefully the actual work involved in moving from old EAC to new isn't too much, but it's a reason why we've yet to see any really look to do it. Once the Steam Deck is out though, it should improve, if enough players ask developers to get it sorted, otherwise players may have to resort to a manual install of Windows on the Steam Deck instead of SteamOS 3 to play some of the most popular multiplayer titles.

Article taken from GamingOnLinux.com.
37 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. Find me on Mastodon.
See more from me
The comments on this article are closed.
45 comments
Page: «3/5»
  Go to:

Lofty Jan 9, 2022
I wonder if it would of been better (as in better than the situation we have now) if Valve had forced a VAC requirement on all games that wanted to use anti-cheat solution sold on steam. I trust VAC more than EAC and you at least wouldn't be in the big mess we have now, besides you would already be on steam and it would be less invasive. I don't think it should be a requirement for those game that don't need or want an anti-cheat. Your software your choice I guess.


Last edited by Lofty on 9 January 2022 at 3:46 pm UTC
1xok Jan 9, 2022
Easy Anti-Cheat isn't easy.
Sakuretsu Jan 9, 2022
The thing I really wanna know is:

Was Valve aware of that before they made the claim of "just a few clicks"?

If so then they made a really anti-consumer move. Lying and misleading us with Epic's help.

If like us Valve didn't know about that then I have one more reason to despise Epic, because IMO that looks like blatant sabotage since Epic already knew "nobody" uses that version of their Anticheat.
mr-victory Jan 9, 2022
Which type of EAC does Fortnite use?
Mal Jan 9, 2022
  • Supporter
Quoting: SakuretsuThe thing I really wanna know is:

Was Valve aware of that before they made the claim of "just a few clicks"?

Epic made the "few click away" announcement.

EAC was bought by Epic (not Valve) a few weeks before they announced EGS (and imho when they did, and Tim explained his "gaming vision", it became clear why they bought it. So the actual surprise was that they were supporting proton just because it would benefit gamers, not that they use it as a troyan horse to impose their infrastruture in the industry).



Reading it now it's clear that they didn't outright lie and that they really meant "Epic Game Services -which includes EAC" support is few clicks away. But the press (gamingonlinux on top in this case) wasn't disingenuous when it wrote that EAC was one click away either. Only actual devs trying to make this work know these kind of details, like that the same product EAC has two different libraries with different licenses and stuff attached. I mean, after the articles Epic could just release a statement and let the press disambiguate this. New games will probably use EOS libraries. But there is no way old ones will undergo all the work to integrate it when EAC library works fine for its intended purpose.

But I guess they were just happy to get free PR and then leave to the individual devs to deal with the unrealistic expectations of their fanbase. And possibly create attrition with them (ovbiously it's not just Vermintide, it's plenty of "plz do the few clicks and support proton" threads on EAC games Steam forums).


Last edited by Mal on 9 January 2022 at 7:03 pm UTC
braiam Jan 9, 2022
Quoting: Guest413 games on Steam (link make use of Epic Online Services and don't require an Epic Games account.

Seems that the EOS is for several stuff, not only EAC. And it seems that that stuff is mostly working correctly with Wine. Also, there's a separated list for EAC https://steamdb.info/tech/AntiCheat/EasyAntiCheat/
Purple Library Guy Jan 9, 2022
I'm not going to say I believe this notion, but there is a nasty suspicious part of my mind saying "Huh. Maybe Epic wanted to give Valve the impression that they were playing along with the whole 'Stuff running on Linux well for the Steam Deck' schtick, while actually not doing anything much to help, so Valve would realize too late to do much about it by the time the Deck was released".
So, enable the version few people use, make a glowing press release that's not technically inaccurate but irrelevant to the experience of most actual game developers, and then sit quietly waiting for Valve to realize they've been had, at which point they innocently say "Everything we said was the truth, it's not our fault if it was misinterpreted!"

I suppose more likely it was something more like some Epic exec got some developers and said "OK, Valve have been bugging us to do this thing. Just do the minimum to shut them up, OK? Money doesn't grow on trees (unless you count Fortnite)." And they said "Should we backport the fix to the old version?" "That sounds like extra effort to me."
whizse Jan 9, 2022
View PC info
  • Supporter
It's a clear branding issue. Just rename this new version to Difficult Anti-Cheat and everyone will be satisfied!
Purple Library Guy Jan 9, 2022
Quoting: GuestPeople need to stop making this out to be some conspiracy by Epic, when it
cannot be proven.
Sakuretsu Jan 9, 2022
Quoting: Mal
Quoting: SakuretsuThe thing I really wanna know is:

Was Valve aware of that before they made the claim of "just a few clicks"?

EAC was bought by Epic (not Valve) a few weeks before they announced EGS (and imho when they did, and Tim explained his "gaming vision", it became clear why they bought it. So the actual surprise was that they were supporting proton just because it would benefit gamers, not that they use it as a troyan horse to impose their infrastruture in the industry).

Yeah, I know EAC belongs to Epic.

What I was implying is that Valve, the one pushing Linux Gaming since God knows when, and also the one who have approached Epic in regards to enabling EAC for Proton should have more information in regards to this matter since (I expect?) they have been in touch with Epic for at least some time to even negotiate about enabling Proton compatibility.

Even if Valve didn't make the claim themselves if they already knew about the information we have now and didn't make it clear to the public I still see it as a bad thing.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.