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
The game answer: "Because it would be over-powered and too easy to max out quickly."
Yeah I pretty much push the game to it's limits. I have very few to zero issues despite that with the occasional hiccup.
Generally this shows up an incompatible mod... mod conflicts can be harder to trace.
Try Rimworld Farming in both sets of mods as you split them. And keep splitting until you narrow down the mod conflict. I'll take a look at the mod causing the conflict and figure out why.
@Dressari... the best way to test a mod is by itself. If everything works fine with the vanilla game you've got a mod conflict. That said, Rimworld Farming has worked fine in 1.3 for ages (including debug commands)... so it's strange. How did you narrow it down to Rimworld Farming? 271 mods is a LOT (!!!)