Support us on Patreon to keep GamingOnLinux alive. This ensures all of our main content remains free for everyone with no article paywalls. Just good, fresh content! Alternatively, you can donate through PayPal, Liberapay or Buy us a Coffee. You can also buy games using our partner links for GOG and Humble Store.

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

By - | Views: 57,873

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
We do often include affiliate links to earn us some pennies. We are currently affiliated with GOG and Humble Store. See more here.
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.
See more from me
52 comments
Page: «6/6
  Go to:

Liam Dawe 12 Jan
Quoting: 01dan
Quoting: KoopacabrasI'm not sure if I understand this correctly. So supposedly just updating the EAC version , will automagically enable proton support? or even with the up-to-date version you still have to enable proton support manually?
From what I understand from the article I also have the same question.
Developers first need the EOS SDK version, and then they need to manually enable Proton support in the settings.
Alloc 14 Jan
QuoteOne 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.
Unfortunately that's not true. EOS authentication *has* to be done to use EOS EAC. The users just don't see it, as EOS authentication is independent of an EGS account ;) (Unless they block access to EPIC servers in their firewall or similar stuff, which seems to be the case for some users as we have seen with our game)
Still, it does create an EOS "account" internally that maps your SteamID to that EOS ID, but that's about it. EOS does not get to know anything other than that (and obviously things like your IP while being connected to their backend, the same way that EAC servers would have anyway)

QuoteHopefully 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.
It's not *that* much, but it's still *way* more than flipping a switch as some people read into EPIC's announcements. Well, actually EPIC's announcement was correct *if* you were already using EOS EAC, but for those that have to migrate from legacy EAC it's more due to adding a new framework, including all the steps to authenticate, verify users etc. The EAC APIs themselves are *mostly* the same though.


Quoting: rustybroomhandleIf I were them I would not bother doing the work to integrate a completely different version of EAC. Sounds like they might as well just drop EAC and switch to a different solution like BattlEye.
*That* is definitely way more work though ;)

Quoting: master94gaEAC with EOS that is the new version talked in this article doesn't require any login at all for the users.
See above, it does not require a login but does authenticate with EPIC (i.e. EOS) services. For some users that's indeed too much already, even though EAC is part of EPIC anyway so using EAC alone would have exchanged the same data with them already.

Quoting: rustybroomhandleI also still do not see what the point is of sticking to older anticheat solutions because surely that's the one thing you need to be up to date.
The security features from EAC update on the backend without a game dev doing updates to a game. It's just the integration with the game that the game devs need to update themselves.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: Liberapay or PayPal.

This ensures all of our main content remains totally free for everyone with no article paywalls. We also don't have tons of adverts, there's also no tracking and we respect your privacy. Just 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!
Login / Register

Or login with...
Sign in with Steam Sign in with Twitter Sign in with Google
Social logins require cookies to stay logged in.