Hi guys.

 

First of all you'll have to forgive me if I'm not too up on this whole "Why we now have to use Registry" methods instead of unlocalised names (if it wasn't broken why fix it? But anyway...)

 

I registered a block in my mod as a singular block for testing purposes and everything was fine. I have since changed its parent class to allow it to have variants and it's here I come unstuck.

 

First issue I faced was the ModelBakery throwing a null pointer when I tried to call registerItemVariants().

 

Second issue is this registry problem. I've looked at the code for this and there's no way round it. My block can't be registered again despite that version of it no longer existing.

 

Any help would be appreciated. Thanks guys!

 

^{final String colours[] = { "White", "Black" };}

        ^{ResourceLocation[] resLoc = new ResourceLocation[2];}

        ^{for(int i = 0; i < 2; i++)}

            ^{resLoc = new ResourceLocation("barrels:barrel" + colours);}

        ^{ModelBakery.registerItemVariants(Item.getItemFromBlock(BarrelsBlocks.barrelWhite), resLoc);}

 

^{public static Block barrelBlock = new BarrelBlock("barrelBlock");}

    ^{public static Block barrelWhite = new MetaBarrelBlock("barrelWhite");}

 

    ^{public static void createBlocks() {}

        ^{GameRegistry.register(barrelBlock.setRegistryName("barrelBlock"));}

        ^{GameRegistry.register(barrelWhite.setRegistryName("barrelWhite"));}

 

        ^{GameRegistry.register(new BarrelsItemBlock(barrelBlock).setRegistryName(barrelBlock.getRegistryName()));}

        ^{GameRegistry.register(new BarrelsItemBlock(barrelWhite).setRegistryName(barrelWhite.getRegistryName()));}

 

    ^}

ModelBakery.registerItemVariants(Item.getItemFromBlock(BarrelsBlocks.barrelWhite), resLoc);

GameRegistry.register(new BarrelsItemBlock(barrelWhite).setRegistryName(barrelWhite.getRegistryName()));

 

How do you expect

Item.getItemFromBlock()

to return anything other than null before you've told the Item registry what the ItemBlock is?

I was registering the ModelBakery in a block render register class, not the block registry class.

 

How did you expect me to know it was supposed to go in block registry when there's no documentation on it?

 

But I'll try it. Thank you for the response.

Yes I respect and gathered that from doing this revolutionary thing known as reading for myself...

 

I simply mentioned it because I know it probably wasn't clear in the code snippets that they were in seperate classes which was my bad.

 

The simple reason I'm using ModelBakery is the distinct lack of 1.9 method change explanations both in code and online. Therefore, I'm using it as it was what worked in 1.8.9.

 

I will investigate the ModelLoader method you suggest. Thanks for the advice.

 

I still have the registry problem however which is getting on my nerves purely because I can't even test to see if I've fixed the render issue until it decides to register properly.

I fixed it guys...

 

I was so used to setting an unlocalised name in the block constructor class I stupidly changed it to setRegistryName in there and was trying to cast it twice.

 

Everything is working fine... including your disliked ModelBakery method.

 

This can be marked as solved now.