MC 1.12 registering items, blocks.

[winnetrie]

I saw in the manual something about the new registering stuff, but do not fully understand how that works. I have tried some stuff that didn't worked.

I found a way to register stuff and it works, but i'm not sure if that's the way to go.

It looks like this:

public static Block registerBlock(Block block){
    	
    	ItemBlock item = new ItemBlock(block);
		item.setRegistryName(block.getRegistryName());
    	ForgeRegistries.BLOCKS.register(block);
    	ForgeRegistries.ITEMS.register(item);
    	return block;
    }

I have created this method to register things. I also made 1 for metablocks and for slabs.

I also found out that all blocks that have subblocks don't have their subblocks in the creative tab anymore.

They have been registered and are in the game. I checked this with the /give user modid:limestone 1 0 (or 1,2)

It gave me the required block. In my case limestone (0), polished limestone(1)  and bricked limestone(2)

[diesieben07]

You need to use the registry events, like described in the documentation. If you are not familiar with the concept of events in general, read the documentation for those as well.

[winnetrie]

So i think i understand it more or less.

I create a class that handles all the events for my mod. The manual says it can have multiple events.

Is this recommended or not? Should i seperate some events in an other class?

Also i see i register it like this:

MinecraftForge.EVENT_BUS.register()

Sorry to ask, but where do i put this line? Inside my mainclass i guess? But where preInit, Init or postInit? Or somewhere else?

[diesieben07]

1 minute ago, winnetrie said:

Is this recommended or not? Should i seperate some events in an other class?

This is up to you. You can stuff everything in one class or keep similar events in separate classes. However you wish.

 

2 minutes ago, winnetrie said:

Also i see i register it like this:

MinecraftForge.EVENT_BUS.register()

That is one way, yes. You usually do this in preInit. However you can also use @EventBusSubscriber with static event handler methods, also explained in the docs.