hi there, I believe the feature you mentioned has already been implemented here. As of current, crafting combinators do not attempt to make assemblers craft disabled recipe. However, the presence of unresearched recipe signals do affect the signal priority for crafting combinators - I believe this is what you have observed.
Currently, the get_recipe
result is gated behind the get_highest
function call, which relies on a signal cache mechanism to reduce the ups cost of this mod. For context, get_highest
checks the cache to decide whether the mod needs to scan the circuit network (i.e. is the cached signal still the highest signal? has the signal count changed? if no, then scan circuit), which returns the highest numbered signal for get_recipe
function to be translated into recipe.
To implement your suggestion, crafting combinator will have to abandon the cache mechanism because the highest signal isn't necessary something that points to a valid recipe (enabled recipe). On top of that, whenever the highest signal isn't linked to a valid recipe, crafting combinator will have to fallback to the next highest signal and do it repeatedly until it finds a signal linked to a valid recipe.
Besides, I cannot think of a way that can cache this "highest signal with valid recipe" state using the current cache mechanism. The mod will have to run the aforementioned algorithm (+circuit scan) every update cycle.
TLDR: Due to how the cache works, implementing this will require abandoning the cache mechanism and I do not think it is worth it.