Valve announced a change for Steam today that will make things a lot clearer for everyone, as developers will now need to clearly list the kernel-level anti-cheat used on Steam store pages.
Now if only they could more clearly communicate when games are playable offline.
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.
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
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.
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.
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.
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
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.
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.