the Sim Settlements forums!

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

3.3.0 Task list cost issue

alexmbrennan

New Member
Messages
10
I have been having a lot of trouble with HQ after enabling the new task list, the most problematic of which is that I just figure out why the game refuses to start these upgrades.

For example, the science department reports that 30 of 156 energy is used but the task list reports that I don't have the required 75 energy to start the research project which is obviously incorrect. I tried reassigning staff to update department energy and I used the holotape option to refresh HQ stats but the problem persists.

What is going on here? Is something else blocking the upgrade? If so then why does the task list claim that the issue is department energy? Are the energy stats completely wrong? If so then how I do I fix it?

I have similar issues with the ASAM database upgrade but "normal" room construction appears to work OK.

Edit to add: After I found the option to disable the task list in the holotape (it's not in the settings menu for some reason) I was able to start the projects as expected.

Edit 2: I am starting to think that the above "workaround" might be another bug because I can start all building projects at the same time regardless of department energy as if the "limit by workforce" option were off (I double checked that it's on). I am just going to wait for the next patch to fix whatever is going on because none of the HQ stuff is working.
 

Attachments

  • 20240323155316_1.jpg
    20240323155316_1.jpg
    533.5 KB · Views: 10
  • 20240323155340_1.jpg
    20240323155340_1.jpg
    454.2 KB · Views: 10
Last edited:
Hi, I just ran into this issue myself - it appears to be caused by the wrong resource being flagged as insufficient - it's not energy, but rather caps that should be greyed out. Upgrading the treasury vault fixed this for me. I have raised the issue on our internal tracker.
 
Top