currently, the recipe as a datatype holds a pair of ingredient lists, an input and an output. You can either generate it with cards or make one with the recipe constant and JEI, but some things (like multiple fluid inputs or more then nine item inputs) are functional when generated with cards, but not "allowed" to be made with a recipe constant. I know there isn't much more room in the current GUI, so i'm going to suggest a second, more modular design, that can add a variable amount of fluid, item, and energy inputs and outputs while still keeping it a constant and bringing some of the constant-only features (such as oredict compat) with the flexibility of card methods like recipe.with_IO. This should be labeled something different in the programmer, like "machine recipe" or "modular recipe" while still keeping the original for simple situations or crafting table recipes
Issue type:
Short description:
currently, the recipe as a datatype holds a pair of ingredient lists, an input and an output. You can either generate it with cards or make one with the recipe constant and JEI, but some things (like multiple fluid inputs or more then nine item inputs) are functional when generated with cards, but not "allowed" to be made with a recipe constant. I know there isn't much more room in the current GUI, so i'm going to suggest a second, more modular design, that can add a variable amount of fluid, item, and energy inputs and outputs while still keeping it a constant and bringing some of the constant-only features (such as oredict compat) with the flexibility of card methods like recipe.with_IO. This should be labeled something different in the programmer, like "machine recipe" or "modular recipe" while still keeping the original for simple situations or crafting table recipes