HeckGazer

joined 1 year ago
[–] [email protected] 2 points 1 day ago

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

[–] [email protected] 4 points 3 days 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

[–] [email protected] 26 points 6 days ago

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

[–] [email protected] 64 points 6 days ago

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

[–] [email protected] 6 points 1 week ago* (last edited 6 days ago) (2 children)

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

[–] [email protected] 1 points 1 week ago (1 children)

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

[–] [email protected] 3 points 1 week ago (4 children)

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

[–] [email protected] 4 points 1 week ago* (last edited 1 week ago) (1 children)

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

[–] [email protected] 2 points 1 week ago

You are certainly obsessed so points for accuracy

[–] [email protected] 3 points 1 week ago (1 children)

Going for the DK rings got me enough dupes to last a year and by that point slayer can carry

[–] [email protected] 3 points 1 week ago

Looks like a strawb for sure

view more: next ›