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
You can get a mod's .pak file by searching if the mod exists on the Nexus or CF forums.
Alternatively, you can subscribe to a workshop mod, then go to "C:\Program Files (x86)\Steam\steamapps\workshop\content\211820", then sort by "Date Modified", and the .pak should be inside the most recent numbered folder.
Thanks! I figured that something like that's what i'd have to do, but I wasn't certain.
The reason why they're all named like that is because SB's mod uploader tool, that most workshop modders use, doesn't let you specify the file's name.
I tried this, and the mods do in fact show up correctly as if they are working, but the mods don't actually work it seems. This may just be a mod issue, though. (it is also worthy to note that only 1 of the mods is really visible, I'll try it with something else to see if it works)
Again, thank you for your help!
nevermind, I forgot a dependency, lol. Thanks for your help!