Hi,

I heard the ore compatibility between IC2, BC and some other mod is based on the Ore Dictionary in Forge.

I'm making a new silver ore in my mod and I want it to make compatible with the redpower one.

How can I do that?

 

Thank you in advance.

Seconded.

 

I'm actually reading someone else's code, trying to help her with debugging.  I have the assistance of someone who knows Java, but I personally don't - I'm learning by going through this!

 

But because I don't know how to call on the Ore Dictionary, I'm having trouble sorting out what she might be doing wrong. 

 

I've hunted all over but can't find a good tutorial on 'how to use the Forge Ore Dictionary' - is there one? 

 

If not... could we get one?

 

-Sevi

Ok, Ok I'll make a tutorial.

^God i love you.^

You've taught me a lot about forge and set me on the road to looking at hooks for myself, so thanks.

I figured out how to call it, but I'm having problems with static references and such (it's thoroughly detailed in the support section, but nobody seems to reply.)

Hi, I Googled my way to this thread and just wanted to say thanks in advance for the tutorial!!

Where is the tutorial located?

 

EDIT: Found it: http://www.minecraftforum.net/topic/1010052-creating-mods-methuselah96s-tutorials-8212/

I think i figured it out (I'm new to modding)

 

[glow=blue,2,300]MinecraftForge.registerOre("oreCopper", new ItemStack(myCopperOre));[/glow]

 

put this in your mod's load() method. the above example is for Copper Ore, but you can add anything you want really. though the String parameter should follow the tamplate:

 

"oreMaterial" or "IngotMaterial" or "gemMaterial"

 

in general: "typeMaterial"

 

List of Strings Forge already knows: oreTin, oreCopper, oreSilver, oreUranium, ingotTin, ingotCopper, ingotSilver, ingotBrass, ingotBronze, ingotUranium, ingotRefinedIron, dyeBlue, gemRuby, gemEmerald, gemSapphire, itemDropUranium, woodRubber, itemRubber

Forge doesn't 'know' any of those registries.

Those just happen to be common ones mods use.

All those strings are determined by modders, not forge.

Tutorial here: http://minecraftforge.net/wiki/How_to_use_the_ore_dictionary

 

Methusaleh, if you want me to take it down, i will.  It's format is heavily based off of yours, and I reference your tutorials throughout.

You may wanna checkout build 127, and this:

package net.minecraft.src;

import net.minecraft.src.forge.NetworkMod;
import net.minecraft.src.forge.oredict.OreDictionary;
import net.minecraft.src.forge.oredict.ShapedOreRecipe;
import net.minecraft.src.forge.oredict.ShapelessOreRecipe;

public class mod_OreDictTest extends NetworkMod
{    
    @Override
    public String getVersion()
    {
        return "Boo!";
    }

    @Override
    public void load()
    {
        CraftingManager.getInstance().getRecipeList().add(new ShapelessOreRecipe(Block.dirt, "test", "test"));
        CraftingManager.getInstance().getRecipeList().add(new ShapedOreRecipe(Item.pickaxeDiamond, new String[]{"XXX", " # ", " # "}, '#', Item.stick, 'X', "test"));
        CraftingManager.getInstance().getRecipeList().add(new ShapedOreRecipe(Item.pickaxeDiamond, "XXX", " # ", " # ", '#', Block.dirt, 'X', "test"));
        OreDictionary.registerOre("test", new Item(31001).setIconIndex(1).setItemName("Test1"));
        OreDictionary.registerOre("test", new Item(31002).setIconIndex(2).setItemName("Test2"));
    }
}

Oh my.  Build 127's new functions look amazing.

 

volcomrj, would you like some help with your tutorial?  Namely, how to make your mod use other mods' ores with the ore dictionary in build 120?

Tutorial here: http://minecraftforge.net/wiki/How_to_use_the_ore_dictionary

 

Methusaleh, if you want me to take it down, i will.  It's format is heavily based off of yours, and I reference your tutorials throughout.

 

thx for writing it though at some point i might try to rewrite it a little

Do whatever you want to it, I probably made like 12 other mistakes.

 

This is directed toward anyone with basic know-how.

 

I'm still working in like 97 or something.

Dude.  Should really try and use the latest Recommended Build.

 

Anyways, I've fixed a couple of mistakes in your code and clarified a bit on how registering works.  Will probably add how to use IOreHandler in a bit.

 

Edit: And done.  Hopefully this'll help some people.

It was recommended when i started Physicraft... But I'm updated now, and registerOre() is deprecated in eclipse :'(. (I know that it's useless now).

 

EDIT: Oh I see, you used 120 (recomended), I'm updated to 128, so confusion has set in .

Could someone update that awesome tutorial with the steps for builds 128 and above?

The explanations are pretty priceless for newcomers =)

There seems to be a new way of adding ore recipes now. I am not very sure how to use it yet.

 

Anyone has any idea on how to use the new class ShapedOreRecipe and ShapelessOreRecipe?

From what I gather, just replace MinecraftForge.registerOre() with OreDictionary.registerOre() for registering, and the recipes seem pretty straightforward.  Seems to work for me.

Its not like i gave a freakin example or nothing.. In THIS thread!

Its not like i gave a freakin example or nothing.. In THIS thread!

 

I am REALLY sorry I wasn't paying attention to what you wrote above. Apologies.

Works perfectly now! The code is so much cleaner than using the IOreHandler!

 

Hmm maybe you should add a shortcut method in ShapedOreRecipe called ShapedOreRecipe.add(XXX) to simplify the method so people don't have to type such a long function such as:

 

CraftingManager.getInstance().getRecipeList().add(xx)

No, don't be lazy.

No, don't be lazy.

 

Not lazy. It is for code aesthetic purposes but anyway it's not important. Thanks for adding this new feature. Makes ores a lot easier to handle.