I think this is due to each craftable resource instance (CRI) independently storing its active job and then no other CRI checking if there's already a job happening from a different CRI before creating theirs.
Each CRI should check all other CRIs before creating their crafting job.
I think this is due to each craftable resource instance (CRI) independently storing its active job and then no other CRI checking if there's already a job happening from a different CRI before creating theirs.
Each CRI should check all other CRIs before creating their crafting job.