[2.1.7] Asteroid signal no longer sets crushing recipe

Bugs that are actually features.
cellularmitosis
Inserter
Inserter
Posts: 31
Joined: Sat Nov 02, 2024 8:21 pm
Contact:

[2.1.7] Asteroid signal no longer sets crushing recipe

Post 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 680 times
(blueprint here: https://rocketcal.cc/d1de0f53514ae2df73 ... ea27d0.txt)
Last edited by cellularmitosis on Wed Jun 24, 2026 3:11 am, edited 1 time in total.
User avatar
Nova
Filter Inserter
Filter Inserter
Posts: 983
Joined: Mon Mar 04, 2013 12:13 am
Contact:

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

Post 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?
User avatar
boskid
Factorio Staff
Factorio Staff
Posts: 4802
Joined: Thu Dec 14, 2017 6:56 pm
Contact:

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

Post 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.
Snoggles
Manual Inserter
Manual Inserter
Posts: 3
Joined: Tue Aug 11, 2026 12:41 am
Contact:

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

Post 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.
Post Reply

Return to “Not a bug”