I am working on total overhaul mod/resource pack and I have run into an issue with a blockstates file. I want to create a custom model for one of the ores in Thermal Foundation and have my model prepared but unlike vanilla Minecraft, Thermal Foundation uses a single blockstate file to manage all of its ores and declares the model at the top level. I am not sure if it is a .json syntax issue I am running into, or whether there is something that prohibits me from declaring the model under the variations. Can someone point me in the right direction?

Here is the ores.json blockstate file.

{
	"forge_marker": 1,
	"defaults": {
		"model": "cube_all",
		"transform": "forge:default-block"
	},
	"variants": {
		"type": {
			"copper": {
				"textures": {
					"all": "thermalfoundation:blocks/ore/ore_copper"
				}
			},
			"tin": {
				"textures": {
					"all": "thermalfoundation:blocks/ore/ore_tin"
				}
			},
			"silver": {
				"textures": {
					"all": "thermalfoundation:blocks/ore/ore_silver"
				}
			},
			"lead": {
				"textures": {
					"all": "thermalfoundation:blocks/ore/ore_lead"
				}
			},
			"aluminum": {
				"textures": {
					"all": "thermalfoundation:blocks/ore/ore_aluminum"
				}
			},
			"nickel": {
				"textures": {
					"all": "thermalfoundation:blocks/ore/ore_nickel"
				}
			},
			"platinum": {
				"textures": {
					"all": "thermalfoundation:blocks/ore/ore_platinum"
				}
			},
			"iridium": {
				"textures": {
					"all": "thermalfoundation:blocks/ore/ore_iridium"
				}
			},
			"mithril": {
				"textures": {
					"all": "thermalfoundation:blocks/ore/ore_mithril"
				}
			}
		}
	}
}

 

 

Edited April 20, 20205 yr by GameSetCrash

My guess is that you're updating this to 1.13+. The ore is registered using metadata. There is no such thing as 'metadata' in that sense after 1.13. So, you have to create a separate block for each ore.