HeckGazer

joined 2 years ago
[–] HeckGazer@programming.dev 2 points 1 year ago (1 children)

There's a small machine at the resource inputs that gets full resource priority and keeps a couple chests full of spoilage handy as well. Eggs decay fairly slowly so it doesn't take that much to keep one circulating.
It's not a perfect solution but saves needing manual intervention for at least as long as it takes me to look back there again

[–] HeckGazer@programming.dev 2 points 1 year ago (3 children)

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.

[–] HeckGazer@programming.dev 8 points 1 year ago

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

[–] HeckGazer@programming.dev 3 points 1 year ago (5 children)

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

[–] HeckGazer@programming.dev 4 points 1 year ago

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

[–] HeckGazer@programming.dev 26 points 1 year ago

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

[–] HeckGazer@programming.dev 68 points 1 year ago

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

[–] HeckGazer@programming.dev 6 points 1 year ago* (last edited 1 year ago) (2 children)

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

[–] HeckGazer@programming.dev 1 points 1 year ago (1 children)

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

[–] HeckGazer@programming.dev 3 points 1 year ago (4 children)

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

view more: ‹ prev next ›