Jump to content

Dup should wait 1 tick after finsihing an errand


DC2
  • Branch: Live Branch Version: Linux Pending

## Current behavior

The dup commits to the next errand immediately after finishing the last errand BEFORE the environment updates.  

e.g. after the cook fills the Microbe Musher with water, they don't realize it's ready to make bush bars in that tick and decide to go outside the kitchen to do other errands. At this instance if you issue a move command to their current position, they will make mush bars. 

Is this related to the new QoL update "Duplicants now prioritize finding a new errand once they've completed their current one. They'll spend less time idling before they get back to work, which will be most noticeable in late-game saves."?

## Desired behavior

The cook should stay in the kitchen, alternating between errands. 

"prioritize finding a new errand" makes sense, but dupes don't need to find a new *type* of errand. Also make sure the game updates errand availability before the dupe makes a decision.

 


Steps to Reproduce

- New game.

- Prepare a Microbe Musher and a Pitcher Pump. 

- Kill all dupes except one. 

- Press L to set high priority to cook (40/50). 

- Issue Mush Bar orders. 

- The cook will start transporting water. 

- After that, issue some other commands e.g. digging. 

- When the water is filled into the Musher, observe that the cook goes to dig. 

  • Like 1



User Feedback


Pretty annoying issue that I come across often as a Solo-Dupe run enthusiast, hopefully they fix this (and the bug of the game deciding that your Colony is Lost when you Trailblazer your lone Duplicant)

Share this comment


Link to comment
Share on other sites



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
  • Create New...