1436

Steam games will now need to fully disclose kernel-level anti-cheat on store pages (www.gamingonlinux.com)

submitted 1 month ago by ampersandrew@lemmy.world to c/games@lemmy.world

168 comments fedilink hide all child comments

Now if only they could more clearly communicate when games are playable offline.

you are viewing a single comment's thread
view the rest of the comments

[-] Retro_unlimited@lemmy.world 102 points 1 month ago

That’s awesome! GTA V just screwed everyone on Linux! What a rug pull.

[-] conciselyverbose@sh.itjust.works 143 points 1 month ago* (last edited 1 month ago)

Adding kernel malware after the fact should entitle every single owner who requests one to a full refund no matter how long has passed.

[-] TipRing@lemmy.world 50 points 1 month ago

Full agree. I do want some kind of policy for games that introduce anti-cheat both during early access and after release. Bricking a game you paid for should offer some sort of recourse.

[-] CaptDust@sh.itjust.works 36 points 1 month ago

I'd really like Valve to take an official policy on post-release changes that break games, but for what it's worth they have not given me any hassle with refunds in these scenarios.

[-] nekusoul@lemmy.nekusoul.de 10 points 1 month ago

Yup. If it's important enough that devs now have to add a disclaimer on the store page, surely devs shouldn't be allowed to circumvent that by adding it later. Since SteamDeck customers are affected by this the most, it's weird that this isn't already a rule, particularly for games that are SteamDeck verified.

[-] theneverfox@pawb.social 1 points 1 month ago

That's a bit much... It's just not possible to guarantee that as a developer

Software is a living thing, and anything useful is made up of layer after layer of ever shifting sand. We do our best, but we are all at the mercy of our dependencies. There are trade-offs, there are bugs we can do nothing about, and sometimes moving forward means dropping support for platforms that are no longer "cheap" enough to afford while also working on the game

I love this though. I also like the idea of requiring access to earlier builds.

These mitigate anti consumer practices - dropping support for a platform is more likely to be a technical trade-off or unintentional consequence though

[-] ad_on_is@lemm.ee 1 points 1 month ago

I do agree with the part where software moves, dependencies yada, yada... I'm a developer myself.

But.. this is different. They eliminated a perfectly working game, where they didn't have to invest a minute of labor to get it working on Linux. The only thing they had to provide was the .so-file (for EAC) when publishing to Steam.... Valve did all the work to make EAC compatible on Linux, yes, on user-level... but still... it fucking worked.

Punishing an entire userbase, because other assholes (assumably) used Linux for cheating is discrimination. Even if there were no cheaters at all... it's still discrimination... because it used to fucking work.

[-] theneverfox@pawb.social 1 points 1 month ago

Oh no, I totally agree with you that this is gross behavior - I just think your rule is too broad.

So we need more focused rules and mechanisms. I think disclosing anti-cheat on the store is a good mechanism, I think forcing them to provide previous releases is a good rule. That obviously doesn't cover nearly enough, but in the current gaming environment I think it's a good start

[-] PM_Your_Nudes_Please@lemmy.world 15 points 1 month ago

That’s exactly what Valve did. The automated refund system wasn’t available, but you could request a manual review and cite the added anti cheat; Valve was refunding those who did so.