HeckGazer

For shutdown I have a few circuits monitoring the inputs/outputs to check if we're getting backed up or running dry on either of the fruits. If that's the case the input belts are stopped, egg->egg duplicator inserters are disabled and the chests that hold the one egg being recirculated go into trash mode.

There is a separate unit that constantly ensures there are at least a couple eggs avaliable and "requests" (buffer chest) any excess and is surrounded by turrets.

During startup (science below limit and ingedients on input belts) the spoilage->nutrient inserter is enabled which priority feeds just the first three chambers that make flux. Once any flux has been made (>0 flux on the belt || flux->nutrient machine working) the spoilage inserter stops. That's enough for the flux->nutrient machine to start and the whole system becomes self sustaining.
As part of startup a requester chest requests 1 egg, the rest of the egg duplicators are setup in such a way that they propagate down the line (a direct inserter between them is enabled if the recirculating chest for the next chamber is empty and the egg->sci inserter gets disabled). Once there are eggs in the recirculating chests the startup is considered complete and the requester chests turn off.

There's also a chest that pulls from the main nutrient line to make sure there's always loads of spoilage ready for a restart.

Valheim <3

That circuit networks can be useful for things other than just making CPUs and jukeboxes

I love hearing about this perspective. I 100% agree on bringing bots to every planet but found gleba to be the most belt intensive (not using the most belts but using the most belt tricks).
I think I only used bots to handle saving restart spoilage and removing eggs on factory shutdown/resuppling the initial one on startup

45 hrs

I originally used splitters but then switched to just filtering the inserters pulling from the loop. Since the loop recycles anyway it didn't matter if they missed some/the splitters felt like overkill.
For overflow I had inserters controlled by logi levels feeding into recyclers

To be fair Intels aggressive marketing of failing chips and terrible remediations is contributing to AMDs success right now

Took me a good 5 seconds of thinking this was a fantastic shitpost before I saw what OP meant, good post

Start using them, they might regain momentum.
My favourites are overmorrow and yesternight

Interesting, I'll have a look into it. Thanks

I have it in a bottle, works great. I just wish the resolution wasn't so ass

I love seeing all the different approaches to this. My solution was to break all the recipes up into dependency tiers (coils & gears T1, circuits T2, inserters T3 etc.), which would then let me use the sorting on the advanced combinator to sort the execution. I guess it kinda works how the player crafting queue works:

counter cell holding an index
If logi_requests[index] is not craftable: increment index (counter resets at logi_requests.len)
If we "lock on" to something craftable we save it to mem
Calculate the total resources required (raw and intermediates) using lookup combinators and have that all on a line
Raws get requested, intermediates get "oned out" by a decider and then multiplied by the tier values.
That then gets picked by an advanced combinator which is sorting it by low to high and sent to the assembler.
It then makes as many as needed before moving onto the next thing until eventually it satisfies the saved logi request
It then resets the counter and everything starts again.

I liked that it was resilient to constantly changing network requests and made efficient use of the logi bots with bulk requests