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)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Help us translate Steam
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.