安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
If you want easier plasteel, check out Rim of Madness - Bones.
They have a recipe for processing bones into various materials.
Including calcium polymer, which can be used in combination with steel in a Biofuel Refinery to make plasteel.
That is my preferred method of obtaining it.
Secondly- while lesser than this mod, there is Vanilla Chemfuel Expanded - Unofficial Expansion mod for 1.5. It really only allows to craft some vanilla items (synthetic clothes, plasteel and neutro) from deepchem.
Helps to scratch that itch is anyone is interested in manufacturing materials from oil until this mod gets updated to 1.5
iit would make more sense if we could produce neutroamine
If a mod I use is simply not compatible, it's my problem. Of course I'd always be happy if you could ever support it - but please take whatever time you take or never do it.
There is so much I'd love to see in this mod, like compatibility with Vanilla Expanded Chemfuel or other pipe mods, I just need to live with wishes being wished :) I use all your mods and totally love the bigger variety in materials. Hope you are going to continue them for a long while.
The whole Rimworld modding community is making this game so unique, I'm having so much fun!
1) the VCE patch needs updating because gourmet meals no longer use comp VanillaCookingExpanded.CompProperties_StackByCondiments but instead want thingClass VanillaCookingExpanded.GourmetMeal
2) the Oil Extractor throws an error when generating its inspect string: MissingMethodException: GenDate.ToStringTicksToPeriod. Since that method does still exist my best guess is that the problem would be resolved by recompiling against the new .dlls