Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
i dont do betas and stick with stablility until the next patch is tested by the players.
players will find more bugs way faster than beta testers do.
Its not opting into a beta... its where you go to revert back to Patch 7 so things work as they did before.
Different game, but this is a true story.
I had two installs, one that was steam, one that wasn't. My steam install was my clean install. My other one was for mods--It was extensively modded, including my own projects.
For years, I had no issues. Steam updated when I told it to. The steam version would update when I launched it, the other one would never update, ever, because when an update would run, it would only update the steam one. For years, I had two separate installs, with two different updates.
Until one day, I didn't. One day, steam somehow found my other install, not even on the same drive mind you, and overwrote it with the newest update *and* updated my steam one too /and i didnt launch either of then/
oh but it gets better. I had backups. Any modder would. All my backups were wiped, including WIP projects. And the ones that weren't were incompatible to the point there was no path forward. I got completely bricked.
I know this isn't a BG3 story. It's a steam updating when it shouldn't story, and the lengths at which its actually capable of updating without your consent.
Just to reiterate, I know what i'm doing, It worked perfect for years; until one day it didn't. The only, and I mean the only way to be 100% sure this never happens is to keep your install on a removable drive that Steam can't see or touch.
If you want to stop updates find this file "appmanifest_1086940.acf" in your steam Directory Right click on it and click properties and check read-only. That will permanently stop updates. This works on any game for steam you just have to identify the right file for what ever game you don't want to update.
the default location for that file is
C:\Program Files (x86)\Steam\steamapps
Judging by the other forum posts, the update, as expected, has broken the mods and is not stable in general. I suppose, only the sheer number of players with diverse configurations can help to detect more defects, but being a paying tester for a AAA title is decidedly unpleasant.
Also GOG does not auto-update, which is one of its main advantages in comparison to Steam.
I'm still running Cyberpunk 2.13 (because mods) and it's been that way for months.
But if it somehow does get updated, yeah you can always run the last Patch 7 Beta. Not a beta, but using Steams 'beta' function to play, well 'beta' versions in advance..., so I guess they call it 'beta'