Search Results
8/1/2025, 1:00:44 AM
>>533421864
It's not that hard once you start addressing it in ways it understands.
>I have an assembler being fed train tracks, red modules, and electric furnaces. I want it to stop grabbing tracks when it hits 30.
When Each(assembler contents) ≥ Each(constant combinator-listed values), output Each(inserter blacklist ("Set Filters"). 1 Decider Combinator/assembler. If you're outputting ingredients as a signal from the assembler, double the value from the constant combinator, either manually, or with an arithmetic combinator.
You can use an indexer to cycle through matching sets of data if you feel like getting clever.
>I finally get the fucker to work so I copy paste its setting to all of my other assemblers and inserters. Now all the of them aside from the first are refusing to grab the red modules.
Sounds like a crossed-wire issue.
>Why? Literally how hard would it be to simply have a setting that says "take only what you need to craft 1 of what this assembler produces at a time(check/ uncheck)"
Assemblers don't control what they receive. They just place restrictions on inserters, which already do you a favor by refraining from jamming stones directly into your Production Science assembler or putting an infinite number of plastic bars into your advanced circuit assembler. Keeping them from putting together a stockpile in advance is just an optional last step in optimization, and it's kind of questionable, seeing as the stockpiled resources don't affect the rate of consumption. It's like trying to optimize your way out of a down payment.
Also, Each(Contents) x (-1) to inserter whitelist ("Set Filters") along red, with constant combinator providing a recipe-matching value to all of them along green.
So yes, you can give that literal instruction to the machine anyway, provided you consider the inserter to be part of it, and not just some glutton-enabling innocent.
It's not that hard once you start addressing it in ways it understands.
>I have an assembler being fed train tracks, red modules, and electric furnaces. I want it to stop grabbing tracks when it hits 30.
When Each(assembler contents) ≥ Each(constant combinator-listed values), output Each(inserter blacklist ("Set Filters"). 1 Decider Combinator/assembler. If you're outputting ingredients as a signal from the assembler, double the value from the constant combinator, either manually, or with an arithmetic combinator.
You can use an indexer to cycle through matching sets of data if you feel like getting clever.
>I finally get the fucker to work so I copy paste its setting to all of my other assemblers and inserters. Now all the of them aside from the first are refusing to grab the red modules.
Sounds like a crossed-wire issue.
>Why? Literally how hard would it be to simply have a setting that says "take only what you need to craft 1 of what this assembler produces at a time(check/ uncheck)"
Assemblers don't control what they receive. They just place restrictions on inserters, which already do you a favor by refraining from jamming stones directly into your Production Science assembler or putting an infinite number of plastic bars into your advanced circuit assembler. Keeping them from putting together a stockpile in advance is just an optional last step in optimization, and it's kind of questionable, seeing as the stockpiled resources don't affect the rate of consumption. It's like trying to optimize your way out of a down payment.
Also, Each(Contents) x (-1) to inserter whitelist ("Set Filters") along red, with constant combinator providing a recipe-matching value to all of them along green.
So yes, you can give that literal instruction to the machine anyway, provided you consider the inserter to be part of it, and not just some glutton-enabling innocent.
Page 1