Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
It's not a bug. That's how Steam workshop works with every game. Some games workaround it by automatically cloning your workshop files but that is messy and leads to regular errors with mod updates.
Note: Aside from the instructions in the sticky that tell you how to copy Workshop mod files to Rimworld's native mod directory, you can use Fluffy's Mod Manager and its one-button solution. (It's a pretty nice tool.) It will copy all the mods you select from the Workshop directory to the native mod directory. You can let those Workshop mods update as much as they want to, as well, with no fear of getting a mod update that breaks a save. Native directory mods supersede Workshop mods even when online.