Hello

 

I'm here again with more advice requirement than actual coding problem. I'm seeing two major styles on how to define blocks and items:

 

- The first one, also used by Mojang, is to create a "superclass" of desired functionality and every detail write in initialization of blocks and items to static properties.

 

- The other is to ceate a class for every item and block that you need, even if it doesn't have major functionality change. (Like creating cusom class for my *Enter Popukar Material Here* Pickaxe, rather than using ItemPickaxe with custom settings)).

 

So what is the better approach? What is better for scaling and not cluttering your environment? Also don't be shy and let me know which style you are using and why.

 

Many thanks in advance.

It depends mostly on what you wanna do. I had 7 blocks that are used for building only and I don't need to tell which one's which, only the texture differs. So, I just made 7 textures and instantiated the same class 7 times with different setBlockTextureName names. An example of your blocks is required for further help I think

Thank you, that's the way I probably will go. I was just curious if there are some used "habits" of some sort for doing that.

It depends mostly on what you wanna do. I had 7 blocks that are used for building only and I don't need to tell which one's which, only the texture differs. So, I just made 7 textures and instantiated the same class 7 times with different setBlockTextureName names. An example of your blocks is required for further help I think

 

Actually you don't even need 7 different block texture names, just use the unlocalized name, and name the texture file that, that's what I do. I have pretty much every block in my mod in a blockHandler class (dont like making and initializing blocks in the main class) And I have a BlockRenderer class for all blocks that just look pretty and have no functionality other than crafting, e.g. metal blocks, ores, decorative blocks etc. Though I do have separate classes for all blocks with function or a tileentity (I would like to know how to have all those blocks in one class too, I know it is possible, I have seen things like mekanism on github, and they have like one main tileentity class, and machines with seperate functionality extend that class, or one main block class and functionality blocks extend it).