Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
When loaded together with the mod "[SR]Realistic Ore Generation (Continued)" the LongRangeMineralScanner patch in Patches/SurveySpeed_Patches.xml fails.
The mentioned mod replaces the list entry "CompProperties_LongRangeMineralScanner" with "RabiSquare.RealisticOreGeneration.CompPropertiesOreScanner".
As you already did a conditional patch for another mod, maybe you are willing to do the same for the mentioned mod.
<mods>
<li>[SR]Realistic Ore Generation (Continued)</li>
</mods>
<nomatch Class="PatchOperationReplace">
<xpath>Defs/ThingDef[defName="LongRangeMineralScanner"]/comps/li[@Class="CompProperties_LongRangeMineralScanner"]/scanSpeedStat</xpath>
<value>
<scanSpeedStat>Hauts_SurveySpeed</scanSpeedStat>
</value>
</nomatch>
<match Class="PatchOperationReplace">
<xpath>Defs/ThingDef[defName="LongRangeMineralScanner"]/comps/li[@Class="RabiSquare.RealisticOreGeneration.CompPropertiesOreScanner"]/scanSpeedStat</xpath>
<value>
<scanSpeedStat>Hauts_SurveySpeed</scanSpeedStat>
</value>
</match>
</Operation>
https://gist.github.com/HugsLibRecordKeeper/f9c36dda1de074f72e8289fda572c405
1) just my mods
2) the error-implicated roster of mods applied to the same save file
3) a brand new save file using the error roster from the very start
4) or a brand new save file using the error roster from the very start, with Big and Small - Framework above Odyssey
Therefore, the actual culprit(s) are hidden elsewhere in your modlist, and whatever is causing the error occurs so far up the chain of logic that's supposed to occur on kill it can't be directly seen in the error log. Sorry.