So, I have a tool that uses the ore dictionary to mine certain ores but Blocks.lit_redstone_ore isn't default in the ore dictionary. I tried adding it with,

OreDictionary.registerOre("oreRedstone", (Block)Blocks.lit_redstone_ore);

in my post initialization event but the game gave me the error,

java.lang.NullPointerException: Initializing game

at net.minecraft.item.ItemStack.getItemDamage(ItemStack.java:265)

at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:454)

at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:432)

at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:431)

at com.slothygaming.obsidiantools.ObsidianTools.postInit(ObsidianTools.java:112)

I'm not sure what it is referring to or if I can even fix it. Anyone able to help?

Maybe you should do this in init(FMLInitializationEvent event) not preInit(FMLPreInitializationEvent event)?

I don't do it in pre. I do it in post. I tried doing it in init but it produced the same error there.

It's because, there is no item for lit_redstone_ore. So just use Blocks.redstone_ore instead.

The problem is that when redstone ore is activated(lit), it won't/can't be affected by my item. Would I just have to put a special exception in my code to handle this or is there another way to do this?

OreDictionary is mainly for crafting, so all blocks are converted to items when registered. Block lit_redstone_ore doesn't have a corresponding item. This caused the exception.

Maybe it's a mistake doing this by OreDictionary.

blockBeingMined.getItemDropped(int, Random, int)

and OreDict that instead?

I have to do it by ore dictionary because many other mods add their own ores and I can't account for every single mod. Using the ore dictionary simplifies this by getting ores registered to the ore dictionary and allows for custom ores to be added to my mod by adding them to a config file. I've decided of just making a special exception for lit_redstone_ore.

@Draco, yes, that's what I am doing.

@Draco, sorry I didn't understand what you said when I first read it. That's not a bad idea and might make it easier. I'll try that, thank you.