安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题










Yes, I just tested it. Safe to add to an existing game (can be added whenever), just make sure that if you disable the mod later, that you have no pawns currently working on the reproccessor (otherwise the pawn working will get stuck when reloading the save without the mod).
""SomeUserName\AppData\LocalLow\Ludeon Studios\RimWorld by Ludeon Studios\Config"
This mod's settings should be "Mod_3277539761_GenepackImprovMod.xml"
So if you wanted to change the merge limit to say 20, you'd add "<genepackMergeMax>20</genepackMergeMax>" between the <ModSettings> tags.
Note: Since this setting is not in the UI, it will remain the same even after changing other mod
settings from the UI.
Its a little bit of a hassle, but is a handy trick for some other mods as well."
As always, validating RimWorld will force mods to update.