Wierd issue with registering ItemBlocks in 1.10

[KeeganDeathman]

Whilst updating, I created the code:

//preinit for(Block block : labstuffBlocks)
	{
		if(labstuffBlocks.indexOf(block) == labstuffItemBlocks.size())
		{
			ItemBlock item = new ItemBlock(block);
			item.setRegistryName(block.getRegistryName());
			labstuffItemBlocks.add(item);
			ModelLoader.setCustomModelResourceLocation(item, 0, new ModelResourceLocation(item.getRegistryName(), "inventory"));
		}
	}

	for(Item item : labstuffItems)
	{
		ModelLoader.setCustomModelResourceLocation(item, 0, new ModelResourceLocation(item.getRegistryName(), "inventory"));
	}

//init

for(Block block : labstuffBlocks)
		{
			if(block.getRegistryName() != null)
			{
				block.setUnlocalizedName(block.getRegistryName().toString());
				GameRegistry.register(block);
				Item item = labstuffItemBlocks.get(labstuffBlocks.indexOf(block));
				GameRegistry.register(item);
			}
		}
		for(Item item : labstuffItems)
		{
			item.setUnlocalizedName(item.getRegistryName().getResourcePath());
			if(item.getRegistryName() != null)
			GameRegistry.register(item);
		}

 

And am adding blocks back in(through commented out declarations) one at a time.

One block, say Manganese Ore, works great! Wonderful!

But adding in more, say Copper Ore and the Circuit Design Table, causes an issue.

First, Manganese Ore's itemblock is remapped to copper ore, leaving manganese ore and the table with no active itemblock model.

 

All three have model files, and the blocks themselves render fine.

What could cause this.

In the past, also, I have used a hash map to store the Block to ItemBlock mappings, but thought this could be causing a block to grab the itemblock one earlier than it should(it wasn't)

[Animefan8888]

Why did you create an ItemBlock map when you could just have a block map then when registering create the instance. Look at my block tutorial if you want i do something similar.

[KeeganDeathman]

I access the itemblocks in other places as well.

 

there's a method already in place  for that isn't there

[Animefan8888]

I access the itemblocks in other places as well.

 

there's a method already in place  for that isn't there

There is Item.getItemFromBlock(block)

[KeeganDeathman]

Well I feel dumb

Thanks

[jeffryfisher]

And am adding blocks back in(through commented out declarations) one at a time.

One block, say Manganese Ore, works great! Wonderful!

But adding in more, say Copper Ore and the Circuit Design Table, causes an issue.

First, Manganese Ore's itemblock is remapped to copper ore...

Are you creating a new world after each addition?

 

Try stepping through your pre- and initialization methods in the debugger, paying attention to what's assigned where. Debugger stepping is much better than naked-eye code analysis for spotting run-time errors.