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






il let ya know if i find something not working properly
So 1 unstable into 1 small (basically stabilizing small cell)
2 small into 1 medium
(plus alternative recipe of 3 unstable into 1 medium for vanilla only)
2 medium into 1 large
and 10 or 11 large into 1 reactor (exact balance is 10.5, so either works)
And of course that would make vanometric cores unnecessary.
When I set building as ingredient, game thinks I want building, not minified building
Minified buildings aren't recognized as valid, only installed buildings.
But when installed, pawns uninstall said building, carry to blueprint and drop it next to it, instead of putting it "in"
It seems game is very confused when you try make buildings from another buildings
Alternatively what must be used is minified versions, but I'm not exactly sure how set those as requirment.
I'll try messing around a bit more, but I doubt my knowledge will be enough to figure out minified use, and google gives out nothing useful.
I had idea for different approach that doesn't use vanometric cores, but minified previous tiers instead (mostly born out of frustration when deconstruction doesn't give cores)
Only issue I can think of is using specific minified buildings as construction resource, but will have to give a try and see how game handles it.
Mostly asking because this mod is already halfway there and it can be repurposed with a bit of tinkering, instead of writting new mod from scratch.
While IfModActive allows you to list multiple packageId and specify them as OR conditions, it does not (as far as I know) allow you to use an AND condition, i.e., "if all of them are installed" as a condition.
Also, if there are multiple files with the same relative path, the one in the last listed folder will be loaded. So, for example, if you have two ResearchProjectDefs, one that always loads and one that loads conditionally, change the name of the conditionally loaded one to something like "ResearchProjectDefs-ModName.xml", This should avoid conflicts.
(Conversely, you can "overwrite" the original file by keeping the conditionally loaded side in the same relative path.)
I hope it helps your work a little. Thanks for making this mod.
Adding the Defs using Patch may obfuscate the error, so we recommend the general method of placing the ResearchProjectDefs for VanometricTinkering in the folder where you always load it.
Because LoadFolders.xml will do the checking of the conditions for you, so you don't need to use Patch ...... which means you don't have to do it in the redundant way I presented it, lol.
Even if you have only one of VFE-Power or VFE-Mechanoids installed, this approach should work, since AdvancedVanometric is required for both.
So, I would like to suggest another way to use LoadFolders.xml.
With LoadFolders.xml, you can select the folders to load by checking if the specified mods have been added to that environment.
It is easy to use and you can find the basic usage by looking it up. So I will show you the syntax to check that either VFE-Power or VFE-Mechanoids is installed.
As far as I know, you can provide the condition "if either VFE-Power or VFE-Mechanoids is loaded" by using the following.
<li IfModActive="VanillaExpanded.VFEPower,OskarPotocki.VFE.Mechanoid">(FolderName)</li>
So I would appreciate it if you could add VanometricBasics to the list of prerequisites for VanometricTinkering.
Also, there is a typo in the Advanced Vanometrics label (there is a space at the beginning of the line).
It would be helpful if you could correct this as well.
(Here the premise is rewritten as VanometricTinkering)
<li Class="PatchOperationConditional">
<xpath>Defs/ResearchProjectDef[defName="VanometricAdvanced"]</xpath>
<nomatch Class="PatchOperationReplace">
<xpath>Defs/ResearchProjectDef[defName="VanometricUltimate"]/prerequisites</xpath>
<value>
<prerequisites>
<li>VanometricTinkering</li>
</prerequisites>
</value>
</nomatch>
</li>
<li Class="PatchOperationConditional">
<xpath>Defs/ResearchProjectDef[defName="VanometricAdvanced"]</xpath>
<nomatch Class="PatchOperationAdd">
<xpath>Defs</xpath>
<value>
<ResearchProjectDef>
<defName>VanometricAdvanced</defName>
<label>Advanced Vanometrics</label>
<description>Repurpose 4 vanometric cores into a single unit.</description>
<baseCost>6000</baseCost>
<techLevel>Ultra</techLevel>
<prerequisites>
<li>VanometricTinkering</li>
</prerequisites>
<requiredResearchBuilding>HiTechResearchBench</requiredResearchBuilding>
<requiredResearchFacilities>
<li>MultiAnalyzer</li>
</requiredResearchFacilities>
<researchViewX>21.00</researchViewX>
<researchViewY>4.85</researchViewY>
</ResearchProjectDef>
</value>
</nomatch>
</li>
However, this research project is set up as a prerequisite for Ultimate Vanometric Capability, which is added by a patch when VFE-Mechanoids is installed.
Therefore, an error will occur in environments where only VFE-Mechanoids is installed without VFE-Power.
There are two main solutions to this
1. Add a patch that conditionally adds AdvancedVanometric to the patch that assumes VFE-Mechanoids.
2. Rewriting the prerequisite for Ultimate Vanometric Capability to other research project in the patch that is applied when VFE-Power is not installed.
Personally, I think #1 is better.