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






For example, when theres a weapon that has a "costList" field, and each node below it is <ResourceName>x</ResourceName>, where X is the count of resources, then its easy to just add one using the node and value fields this mod has
But if im trying to add an ingredient to a recipedef, to the <ingredient> node, each ingredient is layed out as such:
<li>
___<filter>
________<thingDefs>
__________________<li>ComponentSpacer</li>
________</thingDefs>
___</filter>
___<count>6</count>
</li>
How do i test a patch that adds the li node AND its child nodes to the ingredients node?
<li></color>
<def></color>Spine</color><<i></i>/def></color>
<coverage></color>0.05</color><<i></i>/coverage></color>
<depth></color>Inside</color><<i></i>/depth></color>
<<i></i>/li></color>
<li>
< (this is the invalid character)
</li>
in your results. Which is no good
In this case, < is one such symbol. Not sure what def has that as input, it’s already a reserved character in xml.
For example;
I have a mod that adds a building to the game
I then have a mod that patches that building's defs to some degree.
Now if I use this tool to check the def of that building, it shows the original def values of the building but not the actual in-game defs as when the patch is applied.
It's a minor thing but it got me confused for well over two hours thinking my patch didn't apply
I'm pretty sure that's accurate, just double checking! Thanks!
Just ping me if you decide to work on it yourself, I'm open to PRs on all my mods as long as the code is solid and there aren't any potentially performance ruining changes.
Hopefully that bit of digging helps. If implementing it and testing it is still a ways off with that figured out, I could try to submit a PR. Probably about time I get around to setting up an environment for C# development anyway.
So to answer your question, no. This is strictly the combined xml doc before inheritance and before any xml patches. Maybe in the future when I have more time
It makes it annoyingly difficult to use the mod to test a new patch, since I cannot build off of any existing patches. With Unified XML Export defunct, this appears to be the best window into the XML available, but if it only shows me the XML before patches are applied, that usefulness is rather more limited than I'd like.