Ore dictionary custom furnace recipes?

[Koopamillion]

So, I have a block called an electric pounder, it has custom recipes. Anyway, I want it to grind up any "copper ore" that has an ore dictionary name of oreCopper. How would I come about approaching this. This is my custom recipe class:

 

https://gist.github.com/anonymous/0033a376ed1baaaa59dc7fe5c3236820

 

Thanks!

[Draco18s]

You will need a way to add a recipe taking in a string argument, instead of an item stack, and getting all of the item stacks from the OreDict that are registered with that string.

 

OreDictionary.getOres(...)

[Koopamillion]

Ok, but how would I use an itemstack array in this? thanks!

[larsgerrits]

1) You get a

List<ItemStack>

returned, not an

ItemStack[]

.

2) Go through every

ItemStack

in that

List

and check if the input is in that list.

[Draco18s]

What I'd actually do is in the

addRecipe(string input, ItemStack output)

method is get the OreDict stacks there and call

addRecipe(ItemStack input, ItemStack output)

so you're not looking up the OreDict every time the ingredient is checked.

[Choonster]

What I'd actually do is in the

addRecipe(string input, ItemStack output)

method is get the OreDict stacks there and call

addRecipe(ItemStack input, ItemStack output)

so you're not looking up the OreDict every time the ingredient is checked.

 

Forge's ore recipes all store the

List<ItemStack>

for the given ore name as returned by

OreDictionary.getOres

, this list will be updated by the Ore Dictionary if any additional items are registered for this name.

 

Ore Dictionary entries are often registered in the same phase as recipes are added (init), so it's entirely possible that more items will be registered for a name after you add a recipe using it.

[Draco18s]

Ore Dictionary entries are often registered in the same phase as recipes are added (init), so it's entirely possible that more items will be registered for a name after you add a recipe using it.

 

I never do my recipes in init, I always do them in postInit for precisely this reason.  That and IMC messages.