Page 1 of 1

[2.1.7] Asteroid signal no longer sets crushing recipe

Posted: Wed Jun 24, 2026 2:58 am
by cellularmitosis
Previously, to set the recipe for ice crushing, you could send one of three signals to a crusher:
  • Ice Crushing
  • Ice
  • Oxide Asteroid
As of 2.1.7, that list is now:
  • Ice Crushing
  • Ice
This is a bummer, because previously I could do recipe switching without using any combinators, like this ice / carbon platform:
Screenshot 2026-06-23 at 9.50.43 PM.jpg
Screenshot 2026-06-23 at 9.50.43 PM.jpg (1.22 MiB) Viewed 681 times
(blueprint here: https://rocketcal.cc/d1de0f53514ae2df73 ... ea27d0.txt)

Re: [2.1.7] Asteroid signal no longer sets crushing recipe

Posted: Wed Jun 24, 2026 9:50 am
by Nova
Honestly, it's a bit weird that it worked at all because there's not only one recipe for the crusher for oxide asteroid chunks, so the signal is not unambiguous.
Did you research asteroid reprocessing in the meantime?

Re: [2.1.7] Asteroid signal no longer sets crushing recipe

Posted: Wed Jun 24, 2026 9:55 am
by boskid
This was an intentional change. Assembler's set recipe is supposed to select a recipe that produces given item, and given those recipes do not produce asteroid chunks (they produce less than they consume) the recipes are not selected.

Re: [2.1.7] Asteroid signal no longer sets crushing recipe

Posted: Sat Aug 15, 2026 9:15 pm
by Snoggles
Thanks for clarifying.

Could the crusher be made to ignore signals that do not represent unambiguous recipes it can craft?

As of 2.1.14, metallic chunk and oxide chunk set recipe to carbonic reprocessing. Carbonic chunk maps to metallic reprocessing. No chunk maps to oxide reprocessing. Was this specific behavior also intentional? It seems unintuitive, especially given the previous behavior.

Setting filters for collectors and recipes for crushers on the same wire would be a useful possibility. Currently "collect more chunks, but don't reprocess anything" seems unrepresentable.