Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support multiple machines per recipe #29

Open
lewark opened this issue Dec 14, 2022 · 0 comments
Open

Support multiple machines per recipe #29

lewark opened this issue Dec 14, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@lewark
Copy link
Owner

lewark commented Dec 14, 2022

To reduce duplication, the system could allow recipes to specify multiple supported machines, like allowing food recipes to use either a smoker or a furnace.

This could be handled by making the "machine" field in recipes an array, or by adding a "provides" field to machines that allows them to act as multiple. I'm currently leaning toward using the device-provides method, since it keeps recipe definitions from needing to repeat several machine names. The system already supports virtual slot mapping, which removes any concerns of inventory slots not lining up.

Since smokers are faster than furnaces, it should be possible to prioritize them over plain furnaces as well. A benefit of handling it on the recipe side would be that priority could be set based on the array order. Alternatively, a "priority" field could be added to machines like is already present for storage.

To resolve the same duplication problem for electric furnaces, fuel could be handled as part of the device specification instead of the recipe.

@lewark lewark added the enhancement New feature or request label Dec 14, 2022
@lewark lewark changed the title Only one machine allowed per recipe Support multiple machines per recipe Dec 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant