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
When a mod requires another mod to work they all need to be local, in the appdata folder. There are no extra steps. You can try making a mod pack by copying the contents of each mod into a new folder you create. If it just copies it's good to go. I cancel the copy anything other than the thumb image and meta file try to overwrite. It's more work that can be a tedious pain in the ass to do when the copy process asks about overwriting. The thumb and meta file doesn't matter, the other files do.
The ID is always there in a file. The game uses the IDs in the SBC files for the saved games. The number IDs are used because workshop items can have the same name. They can't and won't have the same ID.
secondly, it appears (so far) that each mod has a thumbnail in its folder, this thumbnail is usually the same image displayed in the workshop for the mod itself, so by viewing each thumb (so far), it seems it will be very easy to figure out witch mod is witch when you copy them over to the local folder.
could this method be used to eliminate the need to track the steam id of the workshop items/mods? insofar it appears so!
Thanks Jack, great hints, information and bloody good ideas to follow. Champion !!!!