Enhance Selector - Quality Filter with multiple n+1 logical operators like decider.

Post your ideas and suggestions how to improve the game.

Moderator: ickputzdirwech

draslin
Inserter
Inserter
Posts: 24
Joined: Thu Nov 14, 2019 2:27 am
Contact:

Enhance Selector - Quality Filter with multiple n+1 logical operators like decider.

Post by draslin »

I'd like to see the Selector Combinator - Quality Filter behavior modified.

Specifically, I'd like to see a Decider Combinator style interface where I can add as many filters as I want in the same way I can add n+1 conditions in the Decider combinator including specifying the output wire. This combined with allowing the Selector Combinator - Quality Filter to specify a base item type (Or each), an operator (> or < or = etc.) and quality value (statically and/or with a signal specifying quality similar to the quality transfer) would drastically improve our ability to make combinator decisions about quality

In the most basic usage example, I specify a base item, allow all quality out, then on the decider combinator I can use Each knowing only the chosen base item's quality variants will come through for evaluation.

But why? Lets output all firearm magazines. It would be about 2 mouse clicks to select the base item, then specify any quality (same way a splitter would). Trying to use a decider combinator to do the same thing requires about 48 mouse clicks to restrict the signal output to just the firearm magazine and quality combinators. Now multiply that for all ammunition types.

Real world example? Gun ammunition goes in that chest. To setup all combinations of magazines and qualities, would be about 144 mouse clicks instead of 9 for a Selector Combinator connected to an inserter that sets the filters. Now multiply that across all 16 ammo types (magazines, shotgun shells, cannon shells, etc) more than 750 mouse clicks. Vs 32.

I know a parameterized blue print can cut down on that considerably, but it still leaves you with a very static arrangement that would be troublesome to adjust and take up a lot of space to boot. Likewise, you might ask why don't I want the Decider combinator to be able to make quallity comparisons similar to the way the splitter does. Mainly because that would essentially deprecate the selector combinator - Quality Filter.

Edit: Fixed the subject.
Post Reply

Return to “Ideas and Suggestions”