Jump to content

[Q3-327401] Egg Cracker Errand generation issue.


Whispershade
  • Branch: Live Branch Version: Windows Fixed

Issue: Egg Cracker will seem to stop producing errands to crack eggs.

Problem seems to manifest most reliably when using a single egg cracker with multiple forever recipes active. Particularly recipes in which some portion of eggs will be unreachable. Problem less pronounces when prolific quantities of unreachable egg recipe type is moved to an egg cracker with a single active recipe.

20190520150432_1.thumb.jpg.83091a09bb7567eb6fc352dc85967a23.jpg

In the picture shown, two sets of stable facilities will output excess egg production to the output chute over the egg crackers. The stable facilities will create unreachable stone hatch and puft/puft prince eggs depending on the number of active critters in the stables. Excess eggs will be delivered for disposal/consumption. If using a single egg cracker for all egg recipes, eventually the egg cracker will not generate new errands for any available eggs for storage for dupes or automation arm until either game reload or player manually toggles continuous for an egg recipe or increments quantity for egg recipe.

 

Hypothesis: Egg cracker has logic fault when multiple egg recipes are active on a single cracker that prohibits egg cracker from clearing errand for an unreachable/no longer reachable egg and preventing it from generating further errands for reachable eggs. Also noticed problem might be aggravated by running at speed faster than computer can reliably handle, might be race condition symptom.

 

Problem first noticed in Q1 update. Problem remains as of latest build. Noticed other egg cracker bugs, but description seemed limited didn't notice save provided. Providing save that should generator the problem if left to run on its own for some time.

Egg Cracker Demo.sav


Steps to Reproduce
Should be able to run save for a couple hours and see a build up of eggs around egg cracker.



User Feedback


A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.


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...