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










The disabled narratives are by the same mods, with the setting settings, as the two campaigns that didn't have the crash. Possibly something got borked either when refreshing the configs for this run or when I purged and re-downloaded my entire mod folder when fixing a different (actual) problem before I began.
Overall I'm going with *shrugs* weird shit happens sometimes as the reason. The tthing was minor and easily fixed, but the report needed making in case it helps someone in the future however unlikely that is.
The only thing I can think straight up outside of a bad install of the mod is using some sort of mod that disables narrative encounters not jiving with this mod.
Turning this off and finishing for the fifth time leads to no crash so I'm pretty positive it was that erroneous narrative call.
Retaliation Missions usually have this, certain Dark Events cause it and various mods add parameters that make it happen for various reasons.
The vanilla pod people complain about there is usually priest + 2 stun lancers. Maybe the lancers got replaced by hunters.
SpawnDistribution[0]=(Template="AdvCounterOpM1", MinForceLevel=3,