This message:

[11:09:40] [server thread/WARN] [FML]: Unable to lookup ForestMagic:goldenBerylOre for public static com.shieldbug1.forestmagic.block.ore.BlockOreFM com.shieldbug1.forestmagic.init.ModBlocks.goldenBerylOre. Is there something wrong with the registry?
[11:09:40] [server thread/WARN] [FML]: Unable to lookup ForestMagic:magicLeaves for public static com.shieldbug1.forestmagic.block.BlockFM com.shieldbug1.forestmagic.init.ModBlocks.magicLeaves. Is there something wrong with the registry?
[11:09:40] [server thread/WARN] [FML]: Unable to lookup ForestMagic:goldenBerylGem for public static com.shieldbug1.forestmagic.item.gem.ItemGemFM com.shieldbug1.forestmagic.init.ModItems.goldenBerylGem. Is there something wrong with the registry?

appears every time in the preinitialisation stage. When the game is run, the message comes from the Client thread, and when a world is loaded it's from the Server thread. It also appears when a world is being unloaded on the server thread.

 

The blocks and items it mentions work fine, and I didn't register them any differently to any of my other blocks or items.

 

Here is the relevant code:

public static final ItemGemFM goldenBerylGem = new ItemGoldenBerylGem();

// And later, in my method for registering the blocks and items
GameRegistry.registerItem(goldenBerylGem, Names.Items.Gems.GOLDEN_BERYL_GEM);

 

Am I doing something horribly wrong and not seeing it, or should I just ignore the message?

 

 

EDIT: If it matters I'm using forge version 10.13.0.1180 (1.7.10). (I've just been too lazy to update, but I don't think the version has anything to do with this.)

EDIT: I have updated to the latest version of forge (1199) and the message still occurs.

Looking through the FML code that seems to happen when the object you are registering is neither an Item or a Block. Are your classes extending Item or Block?

Well, yeah. Of course they are. They work fine too. And they extend classes that other items and blocks that aren't giving this message extend too.

Alright then I'm not sure. but if they work fine then its too big of an issue but maybe someone else knows how to solve fix it.

I surprisingly just got the same message in my console. I found that the cause was the fact that the variable name and the String name used in the registry were different. If those are both the same then it works fine.

I'll try that when I get home. Thanks