Towdium
commented
4 years ago Thanks for report!
To be clear, the current system always picks the latest recipe you added. Here is the aim: At the beginning of game you add the recipe - 1x wood log => 4x plank. Then at some time you made a sawmill, then you add the new recipe - 1x wood log => 6x plank. I'm assuming the lastest added recipe is the one you want to use.
For the potion recipes, why not just stick to the 3-in, 3-out recipe? Basically you just use some extra bottles, but get some potions (almost) for free. Maybe in theory variable amount of items makes sense, but I don't see practical benefit in this case. Also, variable amount in recipes not only introduces some extra work in calculation engine, but leads to some confusing concepts and user interactions. I need to further consider this idea.
For cauldron recipes, there are ways to handle it nicely, but takes some extra work. You can use placeholder labels to represent aspects. Then use these placeholder labels as input in recipes, making the recipes looks like items => aspects => items. In this case, the usage of aspects will be calculated exactly, then you can find the exact amount of extra aspects in "extra outputs" tab. Let me know if it makes sense to you.
Using the same idea, here is an almost perfect solution for potion recipes: 1 nether wart => 3x quota for awkward potion (as placeholder labels), 1x water bottle + 1x quota for awkward potion => 1x awkward potion. It just requires some extra steps to set up the placeholder labels, but I don't think editing a variable amount will be easier if it is possible. Also, you get the exact amount of how many extra awkward potions you can craft.
Soyaro666
Hey,
I'm currently playing FTB Ultimate Reloaded and added this mod to my client. Now I got the task to brew some potions and ran into a little problem: variable in- and outputs.
I could setup the recipes to require 1, 2 or 3 water bottles and a nether wart to create the same amount of awkward potions I added, but all three variants just are a third of the truth. I thought about adding a nether wart with a consumption of 33% or 34%, which isn't true either, because it would calculate a side output of up to 2/3 of a wart, depending on the amount of potions I want.
I thought of some possible solutions. 1.: The ability to add variable amounts. Maybe you could offer a max amount instead of a fixed amount. So I could save a recipe with "up to 3" as an output. the corresponding input (in this case the water bottles) could get a checkbox for "multiply by amount of output" so the output of awkward potions would be stored as up to three and the water bottles as 1*output-amount. 2.: The ability to define two amounts for an ingredient. Lets look at the nether wart. The brewing stand does in theory consume 33% of a wart per potion, but at least 1 per operation. Thinking about a checkbox again, if a percentage amount is added you could check "waste excess" so the calculator could handle "1 to 3 potions consume one wart in total". this of course could end up in some miscalculations because 3 times 33% isn't 100%, but for amounts below multiple stacks this would work just fine.
Another case I just found is the Thaumcraft Cauldron. There you have to add aspects by throwing in items but most Items have more aspects than needed of even completely different aspects one can't use during the process. These excess aspects can be ignored, generating flux and causing trouble sooner or later, or the excess aspects can be cristallyzed by adding one quartz shard per excess aspect. Here I could think of a mechanic calculating an amount of quartz shards as ingredient, depending of the amount of excess aspects if there are any. One would need a completely new kind of recipe that takes a look at the outputs-view and reacting to aspects being there. Of course one could simply take a look there, adding the amounts shown there and keep that many quartz shards in range but I thought I'd mention that because it's kind of a similar problem: variable but predictable inputs and outputs for recipes.
Of course these are special cases and in 99% of the game one wouldn't care for this features but an additional checkbox here or there doesn't hurt those 99% and the remaining 1% would be glad it's there.