Growthcraft Cellar: Poisoned Booze unable to be crafted.
Nakuta opened this issue ยท 4 comments
Build Version: growthcraft-1.12.2-4.0.4.400.DEV.52b3e0d.jar
Per the changelog/commit list: Added fallback recipe handling for fermentation and brewing.
(22.01.2019) Avatair: See also answer above. Following test steps can be performed:
1. Refresh all brewing/fermenting recipes, by deleting the corresponding configuration files.
2. Ensure allowFallbackRecipes=true in growthcraft-cellar.cfg
3. Perform a fermentation with invalid ingredient. E.g. ferment a fermented wine with nether wart again.
4. Perform a brewing with an invalid ingredient. E.g. brew a fermented wine with hops.
Outcomes should be poisoned wine from 3 and 4.
Tested the above instruction using Purple Grape Wine (Fermented, Wine):
-Nether Wart: Can slot into fermentation barrel, will not ferment.
-Brewer's Yeast: Can slot into fermentation barrel, will not ferment.
-Lager Yeast: Can slot into fermentation barrel, will not ferment.
-Bayanus Yeast: Cannot slot into fermentation barrel.
-Ethereal Yeast: Can slot into fermentation barrel, will not ferment.
-Origin Yeast: Can slot into fermentation barrel, will not ferment.
None of these items would ferment and produce poisoned booze, added as a bug per Avatair.
Could produce correct behavior with success for fermentation barrel:
Has it been tested on a dedicated server or in singleplayer?
If you open fermenting.json, there should exist fallback recipes with item=null for them:
....
{
"comment": "",
"item": null,
"input_fluid": {
"name": null,
"names": [
"fluid_booze_apple_cider_intoxicated"
],
"inclusion_tags": [],
"exclusion_tags": [],
"comment": "",
"amount": 1
},
"output_fluid": {
"comment": "Apple Cider",
"name": "fluid_booze_apple_cider_poisoned",
"amount": 1
},
"time": 24000
},
....
