[1.4.1] Resume terraforming event chain bug?

[Kryndude]

Please go to the following link for an explanation:

https://forum.paradoxplaza.com/forum/index.php?threads/is-this-a-bug-or-is-this-intended.990413/



I'll attach the save file in this thread. "2268.10.15" is the one I'm referring to, but just in case I'll attach the auto-save.

 

[Schimmelpfennig]

Sorry for double posting this, I am repeating my reply from the other thread, adding my save file on top.

Bug? Out of question. Game breaking bug almost definitely.​

Just facing the same bug. Those monsters also gain your pops as garrison troops while purging, plus a double fortification bonus out of nowhere which cannot be brought down by bombardment either - while you get -5% for every(!) pop being purged across your empire.

My 22(!) assault armies (PSI/Clone Commandos, strong, military academy trained) don't have a slightest chance retaking the planet.

In peace you may be able to sit this out and rebuild your empire from the shambles once the purge is over. During war you may as well forget your empire, also if you should rely on ethics needing little divergence as unhappiness skyrocketing may spoil your empire for decades.



Edit: [v1.4.1] (1759) clean start including Leviathan DLC

 

[Risa]

Cause to no bombardment allowed: The controller of the planet is "Deformed Creatures", a "faction" type country. This type of country is technically not at war with anyone, despite hostile to everyone. So bombardment's condition ROOT.OWNER = { is_at_war_with = FROM.CONTROLLER } is not true.
This bug would also affect other always-hostile types of country, such as pirate, adversary, amoeba, crystal, drone, cloud, if they somehow became controller of a planet. (None in vanilla, though.)

Suggested solution: Change that condition (in file 00_rules.txt) to ROOT.OWNER = { is_hostile = FROM.CONTROLLER } .

 

[coyote720]

Cause to no bombardment allowed: The controller of the planet is "Deformed Creatures", a "faction" type country. This type of country is technically not at war with anyone, despite hostile to everyone. So bombardment's condition ROOT.OWNER = { is_at_war_with = FROM.CONTROLLER } is not true.
This bug would also affect other always-hostile types of country, such as pirate, adversary, amoeba, crystal, drone, cloud, if they somehow became controller of a planet. (None in vanilla, though.)

Suggested solution: Change that condition (in file 00_rules.txt) to ROOT.OWNER = { is_hostile = FROM.CONTROLLER } .

I tried this in my current game and it didn't work. I'm hopeful that's because it will only work with a new game. Can anyone verify this one way or the other?

 

[jdrou]

I tried this in my current game and it didn't work. I'm hopeful that's because it will only work with a new game. Can anyone verify this one way or the other?

Can you upload a savegame? Your case may be different. I don't think changes to that file should require a new game. Or you may have made a mistake when doing the modification.

 

[coyote720]

Can you upload a savegame? Your case may be different. I don't think changes to that file should require a new game. Or you may have made a mistake when doing the modification.

I'll include my 00_rules.txt file. The savegame is from before I made the change to the rules text file. When it didn't seem to work, I didn't continue the game nor save it.

Thanks!

 

[jdrou]

When I activate Risa's mod and load your savegame I am able to bombard. Issue might be that you need to leave the is_at_war_with condition in and just add the is_hostile condition. This is what Risa's mod does:

       ROOT.OWNER = { is_hostile = FROM.CONTROLLER }
       ROOT.OWNER = { is_at_war_with = FROM.CONTROLLER }

 

[coyote720]

Perhaps the key is to make these changes a mod. I had changed (after making a backup) the original 00_rules.txt file.

 

[coyote720]

I give up. I have tried everything suggested, but I cannot bombard. I'm pretty new to the game and maybe there is something obvious I'm missing, but I'm totally discouraged. I guess I'll start a new game and simply load an autosave if this happens in the future. It's a shame because it is an interesting event--if it wasn't bugged.

 

[coyote720]

Eureka! Here is what I was doing wrong: I made a backup file of the original 00_rules.txt file, gave it a different name, but I left the backup file in the original folder. Apparently any file in that folder is executed, so the original file was overwriting my changes.

Anyway, I was able to bombard and retake my planet. Thank you so much for the help!