Item texturing without the json file

[Zethariel]

Hello,

 

Simple question, is there any way to simplify the loading of textures to items with variants?

 

I have one item that has dozens of variants, and all I really need is for each variant to have a separate texture - I don't want to have to create a json file for each of them, as it would virtually be just a copy paste of the same, save for changing the ending of the texture name to a different number. There is no model to speak of, just textures that need to be displayed in the inventory screen.

 

Any guidance would be appreciated.

[Zethariel]

  On 3/16/2017 at 11:06 PM, diesieben07 said:

Against intuition Items can actually be bound to use a blockstate json. If you don't provide an item model, forge will fall back to look for a blockstate json and the specified variant in there.

Expand  

So there is no way to purely by code register multiple textures for a single item with metadata-dependent variations? Still need the json file one way or another, and maintain the register + .png  + blockstate.json update?

[Zethariel]

  On 3/16/2017 at 11:14 PM, diesieben07 said:

Yes, bypassing the JSON is a bad idea. Having it all in one file is pretty concise:

 

{
	"forge_maker": 1,
	"defaults": {
		"model": "cube_all"
	}
	"variants": {
		"item_a": [{
			"textures": { "all": "my_texture.png" }
		}],
		"item_b": [{
			"textures": { "all": "my_other_texture.png" }
		}]
	}
}

 

Expand  

Okay, thanks for your time and the example!

[Draco18s]

Note that for 2D item models, you need to copy the item/generated vanilla json and put it inside your block models folder to use as a parent:

https://github.com/Draco18s/ReasonableRealism/tree/master/src/main/resources/assets/harderores/models/block/item

https://github.com/Draco18s/ReasonableRealism/blob/master/src/main/resources/assets/harderores/blockstates/largedust.json#L4

[Zethariel]

Just one fast follow up question

 

  On 3/16/2017 at 11:23 PM, Draco18s said:

Note that for 2D item models, you need to copy the item/generated vanilla json and put it inside your block models folder to use as a parent:

https://github.com/Draco18s/ReasonableRealism/tree/master/src/main/resources/assets/harderores/models/block/item

https://github.com/Draco18s/ReasonableRealism/blob/master/src/main/resources/assets/harderores/blockstates/largedust.json#L4

Expand  

 

If I did it like this, would it be extendable by other mods? As in, could I easily add more subitems with a separate json file that uses the mod I'm making now as an API/library?

[Draco18s]

Other mods? No.

Other items in the same mod? Yes.

[Zethariel]

  On 3/16/2017 at 11:23 PM, Draco18s said:

Note that for 2D item models, you need to copy the item/generated vanilla json and put it inside your block models folder to use as a parent:

https://github.com/Draco18s/ReasonableRealism/tree/master/src/main/resources/assets/harderores/models/block/item

https://github.com/Draco18s/ReasonableRealism/blob/master/src/main/resources/assets/harderores/blockstates/largedust.json#L4

Expand  

I attempted doing what you suggested, but failed. Maybe I'm missing something... registerItems() is called in pre-init, while registerItemModels() in init of the client

 

public final class PonyPowersItemManager {

	public static Item itemSpell;
	
	public static void registerItems(){
		itemSpell = new ItemSpell().setRegistryName(PonyPowers.MODID, "itemspell");
		registerItem(itemSpell);
		
	}
	
	public static void registerItemModels(){
		//Minecraft.getMinecraft().getRenderItem().getItemModelMesher().register(itemSpell,0,new ModelResourceLocation(itemSpell.getRegistryName().toString(), "inventory"));
		registerItemModel(itemSpell, 0);
		registerItemModel(itemSpell, 1);
	}
	
	private static void registerItemModel(Item item, int variantID) {
		ModelLoader.setCustomModelResourceLocation(item, variantID, new ModelResourceLocation(item.getRegistryName().toString(), "spell_type="+variantID));
		
		
	}

	private static void registerItem(Item i){		
		GameRegistry.register(i.setUnlocalizedName(i.getRegistryName().toString()));
		
	}
}

 

in assets/ponypowers/models/block/item/generated.json

{
    "__comment": "Allows blockstates files to use basic item models",
    "parent": "minecraft:item/generated"
}

 

in assets/ponypowers/blockstates/itemspell.json

{
    "forge_marker": 1,
    "defaults": {
        "model": "ponypowers:item/generated"
    },
    "variants": {
        "spell_type": {
            "0":     {"textures": {"layer0": "ponypowers:items/itemspell0"} },
            "1":     {"textures": {"layer0": "ponypowers:items/itemspell1"} }            
        }
    }
}

 

And the textures are there

 

Edited March 21, 2017 by Zethariel

[Zethariel]

  On 3/21/2017 at 10:39 PM, diesieben07 said:

All ModelLoader methods must be called in preInit.

Expand  

Yup, that fixed it, thanks!

[Zethariel]

Can the predicate/overrides be texture exclusive, or must they be done only via models, like the compass is?

 

I was thinking along the lines of:

 

{
    "forge_marker": 1,
    "defaults": {
        "model": "ponypowers:item/generated"
    },
    "variants": {
        "spell_type": {
            "0":     {	
						"textures": {"layer0": "ponypowers:items/itemspell0"},
						"overrides": [
							{"predicate": {"state": 0}, "texture": "ponypowers:items/itemspell00"},
							{"predicate": {"state": 1}, "texture": "ponypowers:items/itemspell00"}
						]
					},
            "1":     {	
						"textures": {"layer0": "ponypowers:items/itemspell1"},
						"overrides": [
							{"predicate": {"state": 0}, "texture": "ponypowers:items/itemspell10"},
							{"predicate": {"state": 1, "texture": "ponypowers:items/itemspell11}
						]
					},
        }
    }
}

 

[Draco18s]

"predicate"s are specifically items. You can't use them in blockstates.

[Zethariel]

  On 3/22/2017 at 9:36 PM, Draco18s said:

"predicate"s are specifically items. You can't use them in blockstates.

Expand  

Shame. But thanks.