So far i have been declaring my items like so

 

public static Item reinforcedStick;
public static Item reinforcedLeatherSquare;
public static Item reinforcedLeatherWing;
public static Item leatherHarness;
public static Item woodenElytra;

 

And i was wondering if it was possible to compress all of that down into an array like this or something similar.

 

item[] itemArray = {reinforcedStick, reinforcedLeatherSquare, ect.};

 

I messed around with it to try and get it to work but was unsuccessful.

So far i have been declaring my items like so

 

public static Item reinforcedStick;
public static Item reinforcedLeatherSquare;
public static Item reinforcedLeatherWing;
public static Item leatherHarness;
public static Item woodenElytra;

 

And i was wondering if it was possible to compress all of that down into an array like this or something similar.

 

item[] itemArray = {reinforcedStick, reinforcedLeatherSquare, ect.};

 

I messed around with it to try and get it to work but was unsuccessful.

What I like to do is add them to a List in a base classes constructor. Then loop through it for registry and model binding. Check out episode 1 or 2 of my tutorials for an example.

And i was wondering if it was possible to compress all of that down into an array like this or something similar.

 

For being able to reference your stuff later, using an array isn't a good idea.  The only time you'd want it is if you were doing something with the whole collection.  Which a number of folks have done for their item registration, but you'd still have the public static properties.

And i was wondering if it was possible to compress all of that down into an array like this or something similar.

 

For being able to reference your stuff later, using an array isn't a good idea.  The only time you'd want it is if you were doing something with the whole collection.  Which a number of folks have done for their item registration, but you'd still have the public static properties.

Yes, agreed you could also use a Reflection way to register IE loop through all of your fields and all instances of Block you register as a Block and all instances of Item you register as an Item.

Which I don't like (or the array for that matter) because it assumes that all of my blocks and all of my items are going to be registered in the same way.  Which they aren't.

 

Which is why I have a whole slew of helper methods for registration (six main methods: Block, Block + ItemBlock, Block + Custom ItemBlock, Block + Custom ItemBlock + Custom StateMapper, Item, Item w/ Variants).

Which I don't like (or the array for that matter) because it assumes that all of my blocks and all of my items are going to be registered in the same way.  Which they aren't.

 

Which is why I have a whole slew of helper methods for registration (six main methods: Block, Block + ItemBlock, Block + Custom ItemBlock, Block + Custom ItemBlock + Custom StateMapper, Item, Item w/ Variants).

I can definately agree with what you are saying, but having an Interface such as I"Modid"Block that has custom methods such as createCustomStateMapper.

 

Or even just include them in the base block class.

Yes, I had to use an interface for the statemapper business. Couldn't find another clean way of handling it.

But no, still no loops other than looping over valid blockstates for registering item renderers.

 

		millstone = new BlockMillstone(); //create
	EasyRegistry.registerBlockWithItem(millstone, "millstone"); //register
	axel = new BlockAxel(); //create
	EasyRegistry.registerBlockWithItem(axel, "axel"); //register
//etc

Yes, I had to use an interface for the statemapper business. Couldn't find another clean way of handling it.

But no, still no loops other than looping over valid blockstates for registering item renderers.

 

		millstone = new BlockMillstone(); //create
	EasyRegistry.registerBlockWithItem(millstone, "millstone"); //register
	axel = new BlockAxel(); //create
	EasyRegistry.registerBlockWithItem(axel, "axel"); //register
//etc

Yes, but that gets quite long and gets harder to find certain blocks. And then you have to specifically register them one by one instead of in mass, by I digress. We are "arguing" opinions not much of a reason to do that.

I'm not sure a giant collection of "instanceof X? do Y" code blocks is going to be any less chaotic.  If anything it splits one logical operation ("Create this block and register it") out across several methods ("create this block" "register it with the game" "register an item block for it too" "register the block's renderer" "register the ItemBlock's renderer").