安装 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(越南语)
Українська(乌克兰语)
报告翻译问题








But this is for 1.5 so it is an easy fix, and worth going over in hopes it helps you get a better idea of how Rimworld deals with xml. This or something similar should be the first patch in the sequence.
From there we still get no errors, but the walls do not have thermal values. This tells us that the match condition isn't being met. In this case it is because you are looking at an invalid xpath. I am not 100% which is the actual cause, but it is either that you can't use an object's parent for a xpath or the parent being abstract and thus not loaded in memory at the point xml patches are applied.
Fixing that by shorting the xpath to just "Defs/ThingDef[defName=...", we get a new error.
The Conditional does not pass on any details do the nested operation, so you do have to give it isn't own xpath. With the final note being that for ti to fully work as you desire, you would have to break up the patches so you are patching one wall/door/item at a time with each pair of patches looking something like this::
Personally, I feel like this kind of patch is a bit overkill for an edge case caused by advanced users. Especially since the error it causes is fairly benign.
I had the exact xpath error, hence added the parent ones and it seemed to be working - no error on disabled embrasures and concrete walls did show thermal properties.
But then again, guess not many people use that additional mod, and no idea if dev is even still maintaining it.
Thanks for looking into it though!