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
It is a bug (or specification?) of Stellaris 2.1.0.
This mod dose not cause or fix it.
in version 2.1 ...
Because, I have checked all txt file of Stellaris and only events controlling sound use these flags (Sound control is not so important).
However, since I've checked only txt file, there may be unnoticed effect in non-txt files or hard coated as exe file.
Do you know those flags have any effect to the algorithm of NPC empires or something else?
Also I had the problem that the other crises empires wouldn't siege the Contingency (AI) Worlds, even when they wiped their fleets. Did you find a way to fix that or maybe it was fixed from paradox?
The former. This mod modifies only event chain, but fleet power is not modified.
And then, it will awake as Berserker in a probability of 100%. It never awake as Guardian (Final Defense Protocols).
invariably? Does that mean whatever happens they will go berserk?
"event crisis_trigger. 1" is wrong.
Please input "event crisis_trigger.1".
(Do not put a space between "trigger." and "1")
@CaptainKampfkeks
Um.., no I can't.
Because I have not used Zenith of Fallen Empires.
This means I can not test play of compatibility patch.
I do not forbid someone make compatibility patch of this mod, but I can not make it.
Am I not supposed to exterminatus the crisis planets if I want to finish the quests? I can't end the Contingency's Ghost Signal unless I blow up their fifth world, but it isn't spawning.
So, it is decided by the setting of End-Game Starting year and crisis.9999 (and luck).
So, in most case, there is time span between ESC crisis and tri-attack crisis.
- If ESC trigger extradimensions crisis, tri-attack mod will trigger Swarm, Conthingency and rampaging Machine FE. But another extradimensions will not be triggered by this mod.
- If tri-attack mod trigger all crisis, ESC will not trigger any more crisis.
Also other crises will not spawn in that save data.
This means that tri-attack mod will not work if ESC crisis event happens before tri-attack crisis happens.
Load order is not relevant.
Tri-attack overwrites vanilla crisis trigger event.
ESC has independent crisis trigger event.
So, both crisis events work apiece in internal processing.
However, when one of crisis trigger events happens, another crisis event prohibited by flag.
No they will not. ESC crisis event triggers only extradimensions crisis.
And, if it happens, other crises will not happen because of flag control.
It is required to make compatibility patch for using both mods together. But, it is not easy.
There are 2 ways to do it.
(1) Using console command
- Input "event crisis.9999" to console and the configuration event is called.
- Select "As Soon As Permitted"
- Input "event crisis_trigger.1" to console and the crisis is triggered immediately in internal processing even if it is 2200 year.
- Crisis fleet will attack your galaxy about 5 years after this processing.
(2) Re-modifying this mod yourself.
- Put this mod in your local mod folder and make required ".mod" file.
- Open "<this mod>\events\crisis_trigger_events.txt"
- Change "end_game_years_passed >= 50" in 18th line. (Also negative number can be set.)