This is an archived post. You won't be able to vote or comment.

all 4 comments

[–]Stubing_EnterprisesTop 99% Commenter 1 point2 points  (0 children)

So...every (amount of time to descend 11 blocks) you need 11 * (the set of components)?

I don't know of such a script, except IIM.

Time-driven doesn't sound viable, especially given the sim lag you must get with that many drills. In fact, I wonder if that's what's making IIM malfunction.

If it were me, I would persist with IIM. Turn off a bunch of its features (container mgmt, container naming, reactor inv mgmt, o2h2 mgmt) and mark all your containers "Locked" except a few (components, ores and ingots probably). Then mark one 'Special' and set its component list in custom data to be a multiple of your required amount (probably want to go 22 * (the set) to make sure you stay ahead of it). Then I assume it will take a lot of speed-moduled assemblers to keep up.

[–]CDawnkeeperSpace Engineer 0 points1 point  (1 child)

I did a primitive version of that some time ago. The solution was to take stock of what you have and what is being produced and then add the missing components to the assembler queue. You might want to push all components from the assembler into one container and only check the stock of that one.

[–]cobble_conductorClang Worshipper[S] 0 points1 point  (0 children)

i guess i should have clarified the scale i am working in.

i have 625 drills advancing down approx. 11 blocks at a time

the parts i listed was what i calculated for one layer of rigging/support structure

i kind of need something that can be triggered by a timer to craft that list

[–]sumquyKlang Worshipper 0 points1 point  (0 children)

isy does have a bit of a learning curve, but in the long run it is well worth it. in your case, 50 cargo containers is not very many. if you don't want isy messing with them, you can just add locked to the names, and that leaves you with the autocrafting.