[Solved][1.8.9] How to change inventory icons of an item based on nbt

[DanielDawn]

So I have a tool that is supposed to change colors based on nbt, and I have this working for the model in the hand. However, the model in the hotbar remains the same. In the past, I've used 

Item#getIcon

Is it possible to change the inventory texture of an item based on it's nbt data? If so, I'd like to know how I would do so. I don't want to use durability because the item is a tool, and having a consumable item used to change its texture damaging it wouldn't make much sense and would mean that if the item were repaired its texture would be lost. 

Edited January 9, 2018 by DanielDawn

[Draco18s]

You need to set the item's custom mesh definition.

I do that here (this code being client side, super being the common code part of just registering the item as normal):

https://github.com/Draco18s/ReasonableRealism/blob/1.12.1/src/main/java/com/draco18s/hardlib/client/ClientEasyRegistry.java#L124-L130

IItemWithMeshDefinition is just an interface that allows my items to define their own mesh definitions, which is done here:

https://github.com/Draco18s/ReasonableRealism/blob/1.12.1/src/main/java/com/draco18s/industry/item/ItemCastingMold.java#L87-L118

In this case, it allows me to select any one of these models:

https://github.com/Draco18s/ReasonableRealism/tree/1.12.1/src/main/resources/assets/expindustry/models/item

[DanielDawn]

So does Custom Mesh Definition use the modelresourcelocation specified? How can I be sure that the models it's using are registered? I keep getting a black and purple box, meaning that it couldn't find a json. 

 

My Platinum_Bow is using this method. It's currently just a placeholder for a different item. I'm testing to see if it even uses the se/models/item/platinum_bow_pulling_2.json and se/models/item/platinum_bow_pulling_0.json. 

@Override
	@SideOnly(Side.CLIENT)
	public ItemMeshDefinition getMeshDefinition() {
		return new ItemMeshDefinition()
		{
			public ModelResourceLocation getModelLocation(ItemStack stack)
			{
				if(stack.hasTagCompound()) {
					NBTTagCompound nbt = stack.getTagCompound();
					if(nbt.getBoolean("platinum")) {
						return new ModelResourceLocation("se:" + SeItems.platinum_bow.getUnlocalizedName().substring(5) + "_pulling_2", "inventory");
					}
				}
				return new ModelResourceLocation("se:" + SeItems.platinum_bow.getUnlocalizedName().substring(5) + "_pulling_0", "inventory");
			}
		};
	}

 

I'm using my regular proxy to do what your easyregistry classes do.

public static <T extends Item & IItemWithMeshDefinition> void registerItemWithCustomMeshDefinition(T item, String registryname) {
		SmallEnhancements.proxy._registerItemWithCustomMeshDefinition(item, registryname);
	}

	public <T extends Item & IItemWithMeshDefinition> void _registerItemWithCustomMeshDefinition(T item, String registryname) {
		GameRegistry.registerItem(item, registryname);
	}
	
	public static <T extends Item & IItemWithMeshDefinition> void registerSpecificItemVariantsWithBakery(T item, ItemStack variantStack) {
				SmallEnhancements.proxy._registerSpecificItemVariantsWithBakery(item, variantStack);
			}
	
	public <T extends IItemWithMeshDefinition> void _registerSpecificItemVariantsWithBakery(T item, ItemStack variantStack) {
				
			}

 

I'm running those inside of my main class's fmlinitevent.

proxy.registerRenders();
		proxy._registerItemWithCustomMeshDefinition((Platinum_Bow)SeItems.platinum_bow, SeItems.platinum_bow.getUnlocalizedName().substring(5));
		ItemStack variantStack = new ItemStack(SeItems.platinum_bow);
		variantStack.setTagCompound(new NBTTagCompound());
		variantStack.getTagCompound().setBoolean("platinum", true);
		proxy.registerSpecificItemVariantsWithBakery((Platinum_Bow)SeItems.platinum_bow, variantStack);

 

I'm clueless as to how to properly use the variant stack especially. I'm really lost. (Also I used 'history' to go to your commits where you barely started using custommeshdefinitions.)

Edited January 8, 2018 by DanielDawn

[DanielDawn]

Thank you, I registered my ItemMeshDefinition and my models were registered I just didn't show them. I also found out that the reason my item was using the inappropriate model was because I was not preventing the default model from loading, no wonder it kept using the default model. Anyway thank you so much for all your help, I'm recently updating from 1.7.10 to 1.8.9, and I hope to update to 1.9 as soon as I can finish this 1.8.9 version. 

[Draco18s]

46 minutes ago, DanielDawn said:

and I hope to update to 1.9 as soon as I can finish this 1.8.9 version. 

1.10 and 1.12 after that? Hopefully in time for 1.13?