Stellaris [(2.7.1) - Dick v3.04 (67e7) - Orion v3.6.1] - Cloud, Snagged federation project breaks if it times out for any member

[SirBlackAxe]

Description
Cloud, Snagged federation project stuck
Cloud, Snagged federation project breaks if it times out for any member

Game Version
EDIT: Earlier report from 2.7.1
EDIT: Earlier report from 2.8.1 (Courtesy of @Rodmar18)
Dick v3.04 (67e7)
EDIT: Issue still present as of Orion 3.6.1

What version do you use?
Steam

What expansions do you have installed?
Utopia, Distant Stars, Ancient Relics, Federations

Do you have mods enabled?
No

Please explain your issue is in as much detail as possible.
The timed project days left counter for the Cloud, Snagged federation project isn't decrementing.

I joined the Common Ground origin AI empire's federation. When the Flocks of Cloud / Cloud, Snagged event triggered I research it as normal, and I was able to find science ships for two of the three other AI empires in the federation with researching the event as their objective (although I didn't manage to catch them actually doing it).

The issue is that it's been quite a few years of in-game time now, and the event is still in my situation log and I still have the timed project alert. The alert is stuck at 1076 days remaining, and that number does not change as time passes. Other timed events pass as normal. I'm playing ironman so I can't roll back time to give you an exact timeline of how long the event has been frozen for.

Steps to reproduce the issue.
Open my save, press play, and watch the timed event alert tooltip fail to count down as time passes.

Upload Attachment
File(s) attached

 

[Rodmar18]

Wouldn't it be the same bug as the one reported here? In my case, the fact that we were a fed of only two made it easier to spot on.

 

[SirBlackAxe]

Issue still present in Orion 3.6.1.

special_projects\00_projects_federations.txt
DISMEMBERED_CLOUD_PROJECT fires federations3.2010 on_success, but has no effect on_fail for if the project times out.

federations3.2010 fires federations3.2013 and federations3.2020 for event_target:discloud_coordinator regardless of choice, discloud_progress += 1
> free the cloud: discloud_fixed += 1 and fires federations3.2020
> Trap the Cloud: no additional effects

federations3.2013 fires federations3.2014 if discloud_progress >= discloud_team(number of federation members who chose to participate)

federations3.2014 fires federations3.2015 if discloud_fixed >= discloud_team, federations3.2017 if discloud_fixed = 0, or federations3.2016 otherwise.

If one or more members times out DISMEMBERED_CLOUD_PROJECT, they won't fire federations3.2010 to increment discloud_progress high enough for federations3.2013 to fire federations3.2014, causing the event chain to become permanent and unresolvable.

---

This can be fixed during gameplay by using the following console command: effect root = { random_federation_ally = { limit = { is_variable_set = discloud_progress } country_event = { id = federations3.2014 } country_event = { id = federations3.2020 days = 719 } } } and waiting 10 days.

 

[SirBlackAxe]

Other possible issues with this event chain include:

• event_target:discloud_coordinator ceasing to exist
• event_target:discloud_coordinator leaving the federation
  • federations3.2013 will fail to set the dismembered_cloud_complete federation flag.
  • federations3.2014 will be unable to fire the conclusion events for participants, since federation.every_member no longer points to them.
  • If they join a different federation then events fired by their former federation will try to complete the event chain in their current federation.
• federations3.2000
  • Is triggered by a member building a research station while the federation is not at war, which may render it inaccessible once members run out of room to expand.
  • The recent_or_current_dismembered_cloud flag preventing the event from happening more than once every 20 years seems redundant with the dismembered_cloud_complete flag preventing the event from happening more than once, period. I'm not sure which is intended.
  • An empire leaving a federation while the event chain is in progress may block the event chain for any future federation they join.
  • The random_list that assigns each country a discloud_<color> flag checks to see if the current country already has it instead of if any other federation member has it.
  • The discloud_<color> country flags are never cleared so if you get the event chain again you may end up with multiple ones.
  • The discloud_progress and discloud_fixed variables are never cleared/reset, so if the same country is discloud_coordinator multiple times they don't start at 0. (Which can happen if they become a member of a different federation.)
• federations3.2001
  • The x4 factor to choose not to participate for AIs with the Ruthless Capitalists personality has no effect because it's modifying a base value of 0.
  • Possibly AIs that don't own a science ship, or have one that can make it to their capital in time, should opt out? Although a way for other members to donate a science ship and have it spawn in their capital might be preferable.
• federations3.2010
  • The effect destroying the nebula_2 discloud_storm will fail to find it if you've changed capital systems.
  • The effect creating the nebula_4 or space_storm_2 discloud_storm doesn't account for the possibility of the system not having a starbase at the moment (which can happen during a crisis)
• federations3.2014
  • Won't fire federations3.2015 if any participant leaves the federation or gets destroyed (or integrated) before completing the project, even if all remaining members chose to fix the cloud.
  • Doesn't end the event chain for any participant who is no longer a member of the same federation as the discloud_coordinator.
• federations3.2020
  • Deletes every discloud_storm in the galaxy regardless of origin or age, so multiple federations having the event chain at the same time delete each others' clouds
• DISMEMBERED_CLOUD_PROJECT
  • Breaks the event chain if it times out since there's no on_fail effect, as discussed above.
  • Does not abort if the country leaves the federation or the federation ceases to exist.
  • Should this account for losing ownership of the system the project is in?

The completion-tracking discloud_team, discloud_progress, and discloud_fixed variables should probably be stored in the federation itself instead of whichever member happened to trigger the event chain. And then you can just use random_member or federation_leader instead of event_target:discloud_coordinator so that the event chain doesn't break if that one member dies, gets integrated, or leaves.

 

[Rodmar18]

I think this is the way to report about bugged event chains that haven't been addressed for years.
I will try with the Manifesti chain, which is potentially bugged as well.

 

[ASGeek2012]

In all the time I've been playing Stellaris, I have NEVER had the "cloud, snagged" project finish properly.