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
This .acf approach doesn't work.
Any changes to the .acf need to be made to the original .acf.%BRANCH%.
With a hard link, the .acf file is overwritten, the hard link is broken, and the .acf.%BRANCH% stays unchanged.
With a symlink, the .acf symlink is overwritten with a new .acf file, and the .acf.%BRANCH% stays unchanged. (Plus with default Windows settings, for dumb reasons, UAC consent is needed to make a symlink.)
So to work nicely with Steam game updates, you can either
- keep track of the previous branch to copy the .acf back to .acf.%BRANCH% before copying the other .acf.%BRANCH% to .acf
- just use a different Steam install folder for a different branch
- separate the different game installs with folder names that are reflected in the .acf, and read the old .acf's folder name to know which branch it is, then overwrite that branch's .acf.%BRANCH%