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
Thank you for maintaining the mod and keeping it up to date.
You're a real one
Sorry! Fixing this asap!
I appreciate that you updated your mod. But why did you drop support for RimWorld 1.3? For all you know, some players could've been subscribed to this (believe it or not, some players still play 1.3 to this day) and, suddenly, their ongoing saved game stopped working due to this update.
Well, I do see that there is 1 Release for 1.3 available on your GitHub. However, that's the old "1.0" version of your mod. It looks to me like it lacks the fixes you made in your mod's v1.01 and v1.02.
https://steamproxy.net/games/294100/announcements/detail/1703951108841054240
Following these instructions, modders can make their mods compatible with multiple versions - even in the case where the .DLL (assembly) is recompiled to be compatible with new versions.
Quote:
Version-specific content should go in a folder named after the version being targeted.
You can do this with the “Defs”, “Assemblies”, and “Patches” folders. Other data types, like textures, are always shared between versions.
If you do not need the multi-version content loading, you place the “Defs”, “Assemblies” and “Patches” folders in the mod’s root folder, just like before.