search

CyclopsMC / IntegratedCrafting

Craft stuff in Integrated Dynamics networks
MIT License
7 stars 6 forks source link

Updating network restart Crafting jobs #99

Closed ZeekDaGeek closed 9 months ago

ZeekDaGeek commented 9 months ago

Issue type:

Short description:

Updating an Integrated Dynamics network causes crafting jobs to restart. Not much a problem with small dedicated crafting tasks, but if you have a large network responsible for your storage, autocrafting, etc. Your network updates frequently and throws off any current crafting.

Steps to reproduce the problem:

Create a system would allow extra input to make crafting fail, Powah is a good option.

  1. Starting set up: image
  2. Add a cable / Remove a cable.
  3. 👀 image

Expected behaviour:

Versions:

rubensworks commented 9 months ago

Thanks for reporting!

rubensworks commented 9 months ago

@ZeekDaGeek Unfortunately, I'm unable to reproduce your problem (with a vanilla furnace setup). Could you give some more details on how you are triggering the crafting jobs exactly. I see a crafting writer in your screenshot, but I'd like to know what aspect is active, and what its settings are.

ZeekDaGeek commented 9 months ago

The Crafting Writer is set to Craft Item -> Variable Cart set to Item: Uraninite. The only changed setting is "Ignore Storage Contents" = true, with the intent of the system to always craft any Uranium in the system into Uraninite.

I attempted to make it simpler to see if it's related to the machine:

image

Any time I place down a new cable on the ID Network an additional Uranium gets exported by the Crafting Interface into the chest, and the Duration in the Crafting Job terminal gets set back to 0:00:00, which I take to mean that it restarted the existing crafting job.

If I take out the Variable Card from the Crafting Writer so no new jobs are being requested and then destroy a cable in the network the job gets canceled.

rubensworks commented 9 months ago

Thanks for the additional info. I managed to reproduce the problem now. Now for debugging it...