#Ready for limited testing, to gather
1 messages · Page 1 of 1 (latest)
Zipfile 0.1.0:
The interface is probably too busy, and should be a dropdown or at least radio buttons so that you can't select "Show info for one recipe" and "Show info about many items or recipes" all at once
@pastel kernel You might be interested
very
the - and × checkmarks aren't very clear what they mean
Yeah. They have tooltips tho: negative, and multiply by input value
Are they unclear even given the tooltips, or maybe it's not great to hide that in a tooltip on a tiny button?
how would they work for different ratios of input ingredients?
given the explanation it makes sense at a surface level
The combinator picks only one recipe (edit: at a time, that is). The "x" checkbox is a little clunky tho: if you set eg "copper cable: 123" then you will get 123x the stats of the copper cable recipe, even though that outputs 2 cables. So you will get an output of "copper cable: 246".
(or -246 if you checked "-" also)
that makes sense
but I'm curious for the Ingredient checkmark
like does it choose from the lowest input count then?
It chooses one signal that represents an ingredient to a recipe craftable in the given machine(s), and then chooses one recipe (or, for the "output all recipes" checkbox, all recipes) that have that as an ingredient
Maybe useful for figuring out how to void stuff?
it's equal to the input signal (or minus the input signal, with -)
instead of being ±1
possibly "output recipe signal" doesn't need x and - though.
my question is then how does that work for example green circuits, if you inputed 3 wires and 3 iron what would it output?
3x circuit recipe.
right so it just simply doesn't take into consideration the cost
Yeah, it just multiplies by the input value, or not. It's mostly useful when the input is a recipe signal.
if you input 4 wires and 3 iron which does it choose for the value?
Whichever one is earliest in the internal signal ordering
alright that makes enough sense
But yeah, I guess one todo is: is there a better way to account for the recipe ingredient/product quantities? Like probably there is
instead of the current x behavior
as for being busy yeah a bit but it's a mod desinged around greatly compacting what would be a massive web of circuits so it is kinda inevitable
tbh ingredient signal seems really janky to use as a player anyways
Yeah. Could make some of the options exclusive and have a dropdown or at least radio field that disables stuff
Yeah. It's basically for voiding stuff, or for making modded furnaces that are assembly-machines act like furnaces again
by setting their recipe to something appropriate to your input items
That does sound like a very useful feature
would need to make sure there aren't duplicate recipes
yeah, TBH the main uses I had in mind were automalls with recipe mode or product mode ... ingredient mode is sorta there because I could
would save me a lot of space on my space platforms
Though probably wouldn't work for asteroid catchers I assume
Yeah, it doesnt know about them
oh and pinging also @lament zephyr
Thoughts on how to make this better / cleaner / more useful for an automall?
Hmm so you input an item, and it outputs the recipe for that item right? Couple questions:
- How do you handle items with multiple recipes?
- Can you have an output that says which types of machines can craft that recipe? It would be nice to throw an error if the automall is trying to craft something an assembler can't make
I definitely like the idea of a multiplier, it's annoying having to manually multiply ingridients x desired amount lol
You configure the recipe combinator with a list of machines, in priority order.
- In "all recipes for this item" mode, the combinator outputs all recipes that have the item as output, that any of the machines in the list can make.
- In "info about one recipe" mode, the combinator picks only one recipe. It will use the earliest possible machine in the list, and it will output an arbitrary recipe (according to the order that get_recipes_filtered returns or whatever) which is supported by that machine and produces that output. In this mode, it can also output what machine to use (from your configured list).
The multiplier component currently has a noticeable flaw: it currently multiplies by the signal, but doesn't divide by the recipe output count. I'm not 100% sure on the best fix ... probably divide by output and round up?
The combinator ignores input signals that it doesn't have info about
divide and round up, yeah
or round down if dealing with ingredients? or ... another checkbox?? heh probably not
lol. trying for now with straight round up
it still doesn't take (intrinsic) prod into account
Asking how to make 123 cables
the nice thing about rounding up vs down is: if you round down, you might be trying to run the recipe zero times, which could lead to confusion since the signal would be "accepted" but not produce output
but rounding up, this can't happen
(T wasn't multiplied by the input in this picture, it was a weird config in the test world)