Installa Steam
Accedi
|
Lingua
简体中文 (cinese semplificato)
繁體中文 (cinese tradizionale)
日本語 (giapponese)
한국어 (coreano)
ไทย (tailandese)
Български (bulgaro)
Čeština (ceco)
Dansk (danese)
Deutsch (tedesco)
English (inglese)
Español - España (spagnolo - Spagna)
Español - Latinoamérica (spagnolo dell'America Latina)
Ελληνικά (greco)
Français (francese)
Indonesiano
Magyar (ungherese)
Nederlands (olandese)
Norsk (norvegese)
Polski (polacco)
Português (portoghese - Portogallo)
Português - Brasil (portoghese brasiliano)
Română (rumeno)
Русский (russo)
Suomi (finlandese)
Svenska (svedese)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraino)
Segnala un problema nella traduzione
Which was never offered, fWiW.
It shouldn't be set by default, of course, but it should exist as a built-in option, for the reason you mentioned, as well as a variety of other reasons -- preserving mods, system compatibility, poor internet connections, and more.
Now I'm gonna bet that some people are gonna come in here and...have less than nice things to say about this suggestion. Before they do, I'd like to repost my usual list of workarounds for how to avoid being forced to update your games on Steam:
0. Set the game to only update on launch. (Do this before other steps. This lets you get warning to prepare things before an update hits.)
1. Launch the game directly rather than through Steam, or somehow run the game without Steam running. (May require tweaking to get them to work wthout Steam.)
2. Launch the game in Steam's Offline Mode. (Reportedly, you may have more luck with this if you run the game executable or a shortcut directly.)
3. Modify appmanifest files (or their permissions, or permissions to the game files themselves) to prevent updates, such as by making Steam think that the updates were already applied. (Look up guides for how to do this. This guide might help, for example. There are other guides for doing this manually.)
4. Back up your game files elsewhere then delete the game files or just rename the install folder. Uninstall the game in Steam and then move/rename the folder back, then launch the game from the folder.
5. Back up your game files elsewhere, let the update apply, then put the old files back into the game's install directory. (Won't help to avoid wasting your internet connection, but will at least preserve your old files.)
6. If you're just interested in playing an older version, you might be able to get it via a Depot Downloader. (Reportedly this might not work anymore, but there's this guide which you can try.)
7. Get a version of the game on a platform that doesn't force updates. Any version of the game that's DRM-free -- or any store that sells their games DRM-free -- can definitely be made to not update. Some other versions/platforms, even ones with DRM, may still let you play without updating too.
Very useful workarounds! Thanks for sharing them with us! Gave you a little award for it as a 'Thank You'. :)
Valve have already decided devs/publishers are the ones to decide when and how their games are updated or not and are only acting as the inbetween delivery system for those updates. This isn't something that is likely to change no matter how many reasons you can think of for why you don't want to update so its better to try and encourage the individual devs/publishers to use the system that already exists.
@ Slacoon
Developers can enable version choice via branches for the products they own. It stops auto-updating yet as always those who use the narrative of "Steam forces updates" are aware of the option but deliberately and knowingly overlook that when posting.
Exactly, after all it literally is their choice for products they own.
https://partner.steamgames.com/doc/store/updates
Updating Your Game - Best Practices
Furthermore, even if one is already on a branch, any updates to the branch will still be forced onto the player.
And finally, the number of branches game devs can use is limited. Not to mention that, as Eiswolfin pointed out, branches are meant for betas, rather than a repository of old versions.
Frankly, it'd be far more efficient for Valve to fix Steam's design flaw once and for all, rather than for game devs to one-at-a-time implement enable workarounds to deal with this flaw.
But, if we're talking about what's most effective at dealing with this, then managing one's own game installs manually is the most likely to get results. Game devs might not care, or not have the time, or not even speak the same language; waiting for them to solve this problem still means leaving oneself at someone else's mercy to fix stuff.
It's funny how you keep reposting this (and the subsequent quotes which just repeat the same things) like it's some sort of crucifix against vampires, despite it actually saying the opposite of the point you keep trying to make.
The same update, for the same game, made by the same developer, uploaded to other platforms, can remain not forced on those other platforms.
When the only difference in agent is the platform, and the outcome is that it's forced on Steam, that makes it clear that the update is only forced by the Steam client, specifically locking out launching the game when an update is pending.
It not only allows users to opt out of updates it also allows them to rollback versions, set a fresh install to be an older version or choose to partially update to a set stage without going fully to the current build.
* that it's Steam's design that's forcing updates, which is particularly noticeable when the same updates aren't forced on other platforms, and
* that the branch system isn't a thing that just lets people play whatever's already installed on their computers, and isn't a bottomless space for storing old versions anyway.
Version choice via branches is Valve's version of CDPR's rollback feature but of course that has to be overlooked by the advocates of "Steam forces updates" because it breaks their narrative. Secondly version choice STOPS auto-updating. Dead Cells and Hearts of Iron IV are two examples of games on my PC which are still on older versions despite new patches been released by the developers.
Next - misinformation regarding GOG.
False: not all games i have on GOG have rollback as a feature.
And finally "developers force updates" was confirmed in the image and wording on post #7.
Again the issue isn't that Valve have made it impossible for what you wan't to be done the issue is that it is neither ours or Valves choice over if it will be done and those making that choice have chosen not to do it.
Second, any updates to branches are still forced onto anyone on those branches. Also, when branches are removed, those users are then forced to update again. And that's not to mention that moving to a different branch just overwrites any mods.
The image "confirmed" no such thing; heck it even shows the opposite of your point.
Edit: also, oh yeah, where is that quote of Eiswolfin that you posted, from anyway? I can't find it in this thread.
And yet when an update is released on Steam it's still forced on anyone on the default branch -- even when the game has 20 branch versions on Steam.
Two examples from the Skyrim SE forum where end users blame the correct party, Bethesda.
https://steamcommunity.com/app/489830/discussions/0/3362524065551927223/
https://steamcommunity.com/app/489830/discussions/0/3371531159451148267/
As a sidenote if you use mods on Skyrim SE you disable achievements and are warned about breaking the ToS agreed with Bethesda if you re-enable achievements while using mods.
Translation - it is Bethesda game do with as they see fit.