Asteroid collector blacklist filter or target priorities

[protocol_1903]

TL;DR

The asteroid collector should use the target priorities system that turrets use, or have a blacklist filter option.

What?

Currently, the asteroid collector only has the option of a whitelisted filter. This is not very expansive, especially in the case of mods that might add more than four types of asteroids. It would be nice to be able to use a blacklist instead, or use the target priorities system that turrets currently use. Either one would be a
massive improvement to asteroid collector functionality, especially concerning circuit integration.

Why?

It doesn't make sense for it to only have a whitelist option. It would make more sense for it to have a blacklist filter option, or use the same target priorities system that is implemented with turrets.

[sh4dow]

I'd also really like this.

Currently, it's quite annoying to both limit stack inserters to only grab when there's enough of a type stored, as well as filter what the asteroid collector collects.
You need to both send a positive signal for the chunks you currently want (in case none are stored), as well as sending a very large negative signal for types to stop collecting (since some chunks might be still stored in this or other networked collectors). With a blacklist, you could simply send your target amount to be cached as a negative signal, and the collectors would auto-balance (you'd have a single chunk of each unwanted type in the collector network, but that wouldn't matter in practice).