correction d3 is not used.. heh it is just there

as is..

on the IC set

d0 set to the automation module
d1 set to ore mining module
d2 set to salvage or # in the code all references to d2, will still work.
d3 fuel tank..

fuel up rocket, plop chip in, edit what you need with computer, export. turn on IC.. boom.. mine away

I added a multiplier to the ReturnFuelCost to make it think it needs 575 to return.. I had the rocket get lost a lot..

d0 Automated Rocket Automation Module
d1 Automated Rocket Ore Mining Module
d2 Automated Rocket Salvage Module
d3 not used in code
d4 not used in code

how do i set this up?

As some have mentioned here, more details are needed on how to get this up and running to make it all work.

more details and a better description are needed like what circuit does the console need?

@Aterlgnis what i figured out are that d0 = Automated Rocket modul / d1 = Mining Modul / d2 = Scrap Modul / d3 = Rocket Tank / d4 = Console but i don´t know what circuit this need.

Are rockets controlled from the ground? Putting any logic into the rocket does not seem to do anything, while changing settings on ground modules actually seems to affect rocket in space.

Thanks for that IC, it was not clear enough from in-game docs how to use all that (they tend to lack a few details here and there), like which dX'es are for what (i thought db is for command unit and d0 is first module after it, seems i was wrong)

But I wonder, why there are so many places with
> l vari automatedThing %something%
> yield
> l vari %something% %something%
third line in such flow overrides result of first one, so it is just a waste of cpu time...
Maybe it was for some debugging stuff or something, but there is nothing like that now.

Поехали)