Animefan8888

Alsod you need to override setColor because it checks the armorMaterial after looking at the super method.

Ok first off always post all code. Secondly why is this here if you set the color 5-6 lines down and also set the NBT to a new Tag. ((ItemArmor) result.getItem()).setColor(result, 25555555); Are you sure that your Alloy's have those tags?

If you are going to read just a small section, you should read it all. "Loads a different model from the given path, starting in assets/minecraft/models. If both "parent" and "elements" are set, the "elements" tag overrides the "elements" tag from the previous model."

If it is handled in your IRecipe class why do you need onCreated? Post your IRecipe class.

You forgot the [] for elements look back at this link http://minecraft.gamepedia.com/Model

Post your JSON with it in there.

No what I'm saying is onCreated when it is called won't have any color because the NBT doesn't have any color to give it. Have you added crafting recipes yet?

Is there a error in the log? Push new stuff to github.

You are trying to set the color before you even have any color set.

Obviously you add the elements "tag"(not sure if that is what it is called) to you Items Json file and add "shade": false

Also you should be doing all Item/Block stuff in FMLPreInitializationEvent not FMLInitializationEvent.

Don't add your modid to the resource location aka ModelLoader.setCustomModelResourceLocation(item, 0, new ModelResourceLocation("keystand", "inventory")); Also you need to have more than 1 JSON for blocks just so you know.

Where do you actually set the Color Tag? You also need to override hasColor

ChunkProviderSettings Line 239-262 are the default settings for ores.

Check the item model location in minecrafts jar file.

Look at this. http://minecraft.gamepedia.com/Model By far one of the best things I have found for documentation on models.

The file you gave us is a model JSON for an item.

Add them to the OreDictionary it is a class provided by forge

I'm talking about others that have low end computers. But then again, are players likely to have many in one area? If not I guess it is fine, but I would still make the changes at some point.

To use metadata in 1.8+ you need to use blockstates. While blockstates are not limited by amount, metadata is, metadata can only be 0-15(4bits). If you look at wool or even the furnace in vanilla you will see some similarities. These three methods from BlockColored need to be overrided. As you see all of those loop into the field COLOR which is a Property. Blockstates use properties to define what is looks like from the blockstate JSON. You should use vanilla metadata blocks as a reference.

Then here is where you ask yourself Increased lag and easier programmed animations or Normal Frame Rates and harder to program animations?

By sub blocks do you mean metadata? *Edit Allow me to rephrase do you mean wool blocks?

I see you are using addChild to add the existing models to render with the other models. If you remove the ones that you want to color from being a child and add them to the render method you can call Gl11.glColor3f(...) and then after the model.render you can call GLStateManager.resetColor().

Don't do that it may work and all but serious lag can happen from that. Instead please post your code for your model.

I haven't looked at a models code for a while but in there is where the rendering happens find the "cube" that changes color and use gl11.whatever to change the color of that model then afterwards gl11.whatever to change it back.