| 753 | 😟 | Bug | Trying to set up a system where programmed chests are used to request input materials which can then be transportered around into the machines they get processed in and then spit back out into the output chest. Helps cut down on drone traffic as well make some neatly compartmentalized systems. What I'm finding though, is that they'll work for a while and then stop actually requesting inputs.
The programming that I have in the chests is to detect what the first locked empty item is and how many of it will still fit in the chest, then put out a request for that many of that item. (I also then have it sleeping for sixty ticks because the drones have a stroke if you update requests, apparently; and on that note it'd be *really nice* to know how long a tick was in seconds instead of arbitrarily putting in numbers and seeing if it feels long enough or not). Once I noticed this behavior, I also updated it to change the currently signal being emitted to match its request, so that I could see it wasn't just not recognizing it still had space or anything like that.
In the picture, you can see three rows of these modules (top: silica -> silicon, middle: metal ore -> metal ingot, bottom: metal ingot -> metal plate); the input chests are the left ones and the outputs are the right. You can see both looking at then in world and with the one I have selected that it has room for more ore, and it has requested some, and you can see the miner drones on the top of the screen packed full of ore (on network, set to supply only), but the chest isn't actually registering that its request is going to be fulfilled, and none of my runner drones are doing anything either. |  | 2023-08-19 23:57:12 |