Nicholas Thompson

1 year old issue - is there any known fix?

oh of course 🤦🏻‍♂️ So, thats something that might come out of #290 in terms of sourcing recipe data...?!

Have raised this in Burger too as it seems to be missing "upstream"... https://github.com/mcdevs/Burger/issues/35 Seems to be intentionally excluded... https://github.com/mcdevs/Burger/blob/fdff962aeb1aa0351fc222e005af3fa9248345fb/burger/toppings/recipes.py#L136

I'd be inclined to put them in a smelting.json (or similar). They have different structures; in/out/timing. There is no shape, no "count": ``` { "type": "minecraft:smelting", "ingredient": { "item": "minecraft:iron_ore"...

Hi, Based on https://github.com/mcdevs/Burger/issues/35 it's ~50 recipes for smelting. But @Pokechu22 raised an interesting point about smokers and blast furnaces too. They also made this suggestion: > It might be...

That `1.parsed` looks super handy... What package would be used to convert that into `smelting.json`? I've been looking at Burger Burger Extractor... not sure that works with this packer-dumper format?

I'm having issues just getting the burger extractor to work! 😉 ``` (master) % node src/index.js ../Burger/output.json 1.16.2 > Make sure to have the latest version of minecraft-data installed Data...

Thanks @Pokechu22 - so should I use 1.15.x?

ah cool - yes, it worked against a 1.15.2 extraction.

I think I agree... From a UX point of view, I was surprised to not find any "recipes" for iron_ore in recipes.json; it's where I expected them to be (although...