-
-
Notifications
You must be signed in to change notification settings - Fork 386
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
[LookupAnything] Add integration with Extra Machine Config's multiple output items feature #1028
base: develop
Are you sure you want to change the base?
Conversation
Seems like this will get spammy with the 'global byproduct' feature that adds a byproduct to every machine recipes. I'll need to rethink how the UI should work (maybe multiple items on one line), but a workaround for now is probably to exclude those, and only add the per-recipe byproduce. |
To recap, here are the solutions I'm thinking for a recipe that takes A and returns B as a primary output, and C and D as secondary:
I'm still most happy with 1, but I'm interested to hear your thoughts. |
Merged with latest develop, should work now (see screenshot for example from the new Wildflour Atelier Goods, which use this feature extensively. It can also be downloaded to test out). The recipe takes 2 milk and outputs all 4 of the items listed. |
API Reference
For now basically add new recipes with the same ingredient list but new output items taken from EMC's API. It does mean the lookup can't distinguish between "the recipe can produce one of these items" and "the recipe will produce all of these items", but I don't think it's important to distinguish (and any solutions I can think of to distinguish them leads to combinatorics explosions if there are multiple possible outputs for each 'slots'). Plus, this is also how things currently work with building conversion recipes (e.g. Mill).