SpitefulFox

How effective it is depends on how cooperative other modders are. When you register an item with the ore dictionary, lets say... Plastic Ingots, you're telling the Ore Dictionary "Hey, I have some plastic ingots here if anyone wants to use them." Then, if anyone else designs their mod with an Ore Dictionary recipe using "plastic ingots," the ore dictionary goes "Hey, this mod's got some plastic ingots" and makes the recipe using those ingots. The reason why tin, copper, and silver are considered "standards" is because the "Big Mods" like IC2, RP2, and Forestry all use Ore Dictionary Recipes to make any registered tin, copper, or silver interchangeable. So, you can register whatever items you want, but other mods with similar items will have to do their part in order for the things to be interchangeable.

Define "default ores". Just because we currently have a flood of tin, copper, and bronze doesn't mean that further down the line we won't have a billion mods with platinum, lead, and thorium ores in the dictionary instead. This is far too subjective to justify altering vanilla Minecraft in the default API.

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.

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?

Of all the silly mistakes... * slaps forehead * Worked like a charm. Thank you for the quick help. And thank you for Forge.

When installing Forge source and subsequently trying to recompile in MCP, I get the following errors: This is a fresh install of MCP 6.2 and fresh new copy of the source for Forge recommended build 120. The client jar file is an untouched 1.2.5 Minecraft jar without Modloader installed. Is there something I am overlooking?