Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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,