scaper12123

Good to know! Thanks. This'll definitely help as this mod I'm building gets more advanced. I'm only planning on a few ore blocks right now, only a few of which will be shared between dimensions, but as I add more worlds I'll definitely need to get into variants.

Huh, well I'll have to do a bit of experimenting to figure out how to get that to work but until I do, I'm ditching variants. Thanks for your help though! At least I know what was causing the problem now, and I can probably avoid that later with some more experience.

I may as well get an answer to this mystery. Here is what my copper ore looks like: If anyone is curious why I've done it this way, I was following this modding tutorial.

Probably in the realm of 30 for blocks and 60 for items. I'm sure there's a way to consolidate these things but I'm not experienced enough with modding to understand how to do that safely. My format right now, except for that one blockstates file, is for each item to have its own item JSON and for each block to have its own item, block, and blockstate JSON. It's gotten quite cramped in that folder. So for another ore I have that I haven't implemented in my mod atm, Drakolith Ore, I have the following files: I should probably do something to consolidate them into fewer files, but my inexperience and lack of reliable tutorials on how to format mod JSON properly is making this difficult It's possibly both in the case of copper_ore#variant=tin_ore, since I removed the code that allows that to exist. In the case of ores I actually want to exist, i.e. the copper ore that isn't a variant of any kind and just exists like a good little ore block, is likely just missing the model because I have no clue how to format its json correctly to give it an actual model.

OK so as it turns out you're absolutely right and I had not realized that log was there until now. I think I have an idea of what my problem is, but it sadly means I'm going to be rewriting the entire code block that creates my ores. Whelp. Here's the log, if you're curious. What I believe the problem is is how I've coded it or, rather, how the tutorial I follow coded it. The tutorial encourages using variants by using an Enum. However, this originally created problems for me because each type of ore I had created a variant of ore for each of the ores. I.E. For copper ore, I had copper#copper, copper#tin, copper#mithril, etc etc. This turned 6 ores into 36. I eventually fixed this by removing the code that spawns in the extra variants, meaning only one variant would spawn in. I even fixed the issue where the ores had no textures (except for the placed block). However, according to this log the extra variants still exist; the game is just not able to add them cause the code to add them in is commented out. So the code still relies on variants, and it's still getting messed up. So instead of all this debauchery, I'll just code up each of the variants individually. It's more work and more code but, until I can figure out these variant issues, I'll have to go with that. fml-client-latest.log

It doesn't generate an error log though. It doesn't break the game at all; it's the JSON that's the issue. Is there something in this JSON that I'm missing to make this block render?

I can't for the life of me find my issue with these ore blocks I'm trying to texture. Everything is in place, but something is missing to make the blocks render when placed in the world. For my copper ore block, as an example, the item renders fine in the inventory but when placed it gives me the default purple and black with the phrase: "rm:copper_ore#variant=copper" Fiddling around with my JSON seems to have done nothing. This is what my JSON looks like, and if there is other information that needs knowing I'll happily provide it. I just want to understand what my issue here is. For the blockstates, all of my ores are kept in a JSON file I call overworld_ores, a placeholder for when I diversify the locations of this ore. The ores were originally in their own json files named after the blocks, but I tried consolidating them after my attempts to do otherwise failed similarly. I suspect my issue is in this file, since only the block itself is having problems. Then for the block model (of copper ore, for sake of example), I have the following And finally for the item model, I have this: I am absolutely sure that the name "copper_ore" corresponds to the ore block as I intend, since it's showing up as an item correctly. I'm guessing my problem is an issue with blockstate, but any help understanding this would be appreciated.