It may be a crazy or impossible idea, but i could be really useful on advanced automation.
The idea is to optionally write a bit more data on patterns about a recipe. with a button on the terminal to enable or disable it
Describe the feature
When encoding a processing pattern, you have the possibility of encoding more information about the recipe Eg. the recipe map name, maybe other stuff. this information can be passed with the items to the block if it has some interface or something. Every mod would have their own integration to how they handle (or if they handle) that info. For example: gregtech could send data about not consumed items, or the recipe itself (more on the uses), and some kind of crafting input bus could maybe send the recipe directly to the recipe search (recipe search doesn't seem to be a slow thing, but it could be useful).
Ae2 would have their own simple "recipe info getter" to just have the simplest info on the pattern.
Reasons why it should be considered
With integration on mods like ComputerCraft, you could automate some pretty neat stuff, but i think that the best would be to have a button on the interface terminal that could look through the patterns and see if any of them don't exist anymore (much like ae2 already does that for crafting patterns, but it can be CPU intensive to do that all the time, so it would be better to have a button for when recipes get updated).
Additional Context
I think most of the ideas were already put here. It could have some issues with AE2FC but with some overrides. i think it can be done.
I am not an experienced developer, but i know that this may not be easy, still i think it would be pretty useful.
It may be a crazy or impossible idea, but i could be really useful on advanced automation. The idea is to optionally write a bit more data on patterns about a recipe. with a button on the terminal to enable or disable it
Describe the feature When encoding a processing pattern, you have the possibility of encoding more information about the recipe Eg. the recipe map name, maybe other stuff. this information can be passed with the items to the block if it has some interface or something. Every mod would have their own integration to how they handle (or if they handle) that info. For example: gregtech could send data about not consumed items, or the recipe itself (more on the uses), and some kind of crafting input bus could maybe send the recipe directly to the recipe search (recipe search doesn't seem to be a slow thing, but it could be useful). Ae2 would have their own simple "recipe info getter" to just have the simplest info on the pattern.
Reasons why it should be considered With integration on mods like ComputerCraft, you could automate some pretty neat stuff, but i think that the best would be to have a button on the interface terminal that could look through the patterns and see if any of them don't exist anymore (much like ae2 already does that for crafting patterns, but it can be CPU intensive to do that all the time, so it would be better to have a button for when recipes get updated).
Additional Context I think most of the ideas were already put here. It could have some issues with AE2FC but with some overrides. i think it can be done. I am not an experienced developer, but i know that this may not be easy, still i think it would be pretty useful.