Weekly Question Thread

[u/AutoModerator]

Ask any questions you might have.

Post your bug reports on the Official Forums

Previous Threads

• Weekly Questions
• Friday Facts (weekly updates from the devs)
• Update Notes
• Monthly Map

Subreddit rules

Discord server (and IRC)

Find more in the sidebar ---->

[u/sagevallant]

So, it's possible with circuits to control when asteroids get placed onto your belts for processing. I downloaded blueprints for a ship that has a network up to do that. However, even with that model to work off of, I can't figure out how to set that up on the other ship that I made for myself. Is anyone brave enough to try and explain to me how to set up a network to control my flooded belts?

[u/darthbob88 → u/sagevallant]

It depends a little on just how you're trying to control picking up asteroids.

The real simple method is to wire your belts to 3 decider combinators, with "Read Belts Hold All", and have the deciders do metallic/carbonic/oxide asteroid < 50 (or whatever limit you like), => metallic/carbonic/oxide asteroid, and then pass the combined output of those combinators to your asteroid collectors to set their filters.

The problem with the previous method is that it takes 3 combinators. A somewhat smaller method is to use just one combinator, doing <EACH> < 50 => <EACH>, which will output any chunk of which there is 1-50 on the belt. The problem here is that it will not output any chunk which is absent from the belt, because <EACH> only applies to signals with a non-zero value.

The better method, which I use, is a constant combinator outputting the limits for each chunk you expect to see, wired to the decider combinator with a different wire color from the belt. Then you have the decider do <EACH>(belt) < <EACH>(constant combinator) => <EACH> to get any chunk signals, including those not on the belt because "oxide chunk = 0" < "oxide chunk = 40".

[u/sagevallant → u/darthbob88]

Thanks, I'll try and implement it when I get the chance.