[1.10.2] Issue with ore(s) registered with the Ore Dictionary - Missing texture(?)

[ZTagre]

Hello again gents!

   I have an issue that only surfaces in specific situations, so its sorta weird...

 

   I have several ores (namely, a copper ore and a silver ore) that I created and use within my mod, which I also registered

with the Ore Dictionary as oreCopper and oreSilver, respectively. These ores work just fine in my mod; I can see the correct texture(s) when the ore is either in "item" state (dropped on the ground), as well as when it is still in the un-mined (block) state (player has yet to use a pick on it). The respective ingots for each ore type mentioned also display their textures correctly when stored in my inventory, or any chest, etc.

 

I guess what I mean to say here is that, all textures utilized for these ores and the respective ingots, whether in inventory, or in the world, in the item OR block state, all  appear normal whenever my code or vanilla Minecraft interact with them.

 

Also, other mods that are able to utilize copper and / or silver in recipes accept my versions within those specific recipes, without issue.

 

   However, when I go to use my ore in a "custom" furnace (for example) from a different mod than my own, what appears (instead of the expected "ingot" image I registered for it) is that default purple-and-black image, indicating that a texture for my copper or silver ingots can not be found. In a similar way, when the "Void Ore Miner" from the EnvironmentalTech mod "finds" either of my two ores, it also displays the purple-and-black icon, instead of the texture(s) I registered for them! JEI, however, "sees" the correct textures, and I can "pull" ore samples out of JEI that display the correct textures (same with either ingot form...).

 

   Whenever I myself smelt those ores, I get the correct ingot texture(s)! Basically, if I had NOT seen the correct texture(s) after having smelted these ores, I would have known I had a problem with one or more of the textures right off the bat!

 

   I believe that it has something to do with the way I registered my ores with the Ore Dictionary, but I really don't know what I missed! Like I said, everything works as expected when only Minecraft and my mod are operating on these ores, but when OTHER MODS try to figure out what texture is connected to my ore and its respective ingot, I get the familiar (bad) purple-and-black box icon.

 

   Is there some more up-to-date info. on the requirements for properly registering an ore from a custom mod with the Ore Dictionary, or any tutorial tailored specifically to MC 1.10.2 and above? I never really read any tutorial on the "proper" way to do this, and just sorta "winged it",  using another mods source as an example. I was happy when the process I used appeared to work!

 

   Any pointers would be greatly appreciated, as always!

 

   Thanks again in advance,

  ZTagre.

[Cadiboo]

2 hours ago, ZTagre said:

MC 1.10.2

Update. 1.14.2 is out.

[ZTagre]

Not helpful, but thanks anyways Cadiboo :-;

 

   I have a little insight into the issue, but I could still use a little help if any of you are really interested in giving a fellow modder a hand...

 

   As it turns out, it isn't an Ore Dictionary issue at all, but simply a strange way that other mods are treating my items. Whereas I did not assign any metadata value to my ore blocks (for example) when I created and registered them, and by default the metadata value is ZERO when I look at each of my mods items in JEI and press the [CTRL] key, when I look at the ore block that is generated by the Void Ore Miner from Environmental Tech, the value for the ore block is (for some reason) 32767! Why has the "sign bit" of the metadata value been "flipped", and how do I stop that from happening (I know that there must be a way, as it treats the ores from other mods correctly!).

 

   In every case I have seen this problem, I have found that the metadata value for my items has been "modified" to the value 32767!

 

   So, because of this , that block is NOT treated "the same" as my normal ore block, and I don't know why that is happening! Did I need to assign an EXPLICIT metadata value for each item my mod uses, in order that some other mod won't need to "guess", or what the heck?

 

   Where and why did the "Void Ore Miner" give the ore block from my mod a value other than the default?  If I was supposed to provide an explicit metadata value to each item when my mod registered it, I was not aware of this, and for the most part this has not been an issue!

 

   Any REAL suggestions for me? I could really use some insight into this issue!

 

   Thanks again,

   ZTagre.

[Alpvax]

4 hours ago, ZTagre said:

Not helpful, but thanks anyways Cadiboo :-;

These forums only support the latest 2 versions of Minecraft (i.e. 1.14 and 1.13 currently, although due to a special case 1.12 is also still supported currently).

 

RE Your issue, are you using the WILDCARD_VALUE for metadata, because at least at some point in the past that was the value it had.

Unfortunately you aren't going to get much more support than that here, sorry. I would STRONGLY suggest updating.

[ZTagre]

1 hour ago, Alpvax said:

These forums only support the latest 2 versions of Minecraft (i.e. 1.14 and 1.13 currently, although due to a special case 1.12 is also still supported currently).

 

RE Your issue, are you using the WILDCARD_VALUE for metadata, because at least at some point in the past that was the value it had.

Unfortunately you aren't going to get much more support than that here, sorry. I would STRONGLY suggest updating.

Thanks for your response, Alpvax.

 

   After realizing what the value 32767 actually REPRESENTED (the WILDCARD_VALUE for the damage value matching), I was not SO surprised about that particular value; however, I have NEVER set any of my ORES or ITEMS to any metadata value but ZERO. I checked that out thoroughly. I DO, however, admit that, in the case of the ORES and ITEMS in question, I might not have supplied ANY "default" value for metadata myself at all!

 

   Some of my ores (those that "dropped" items other than themselves [in the "block" state] when mined WERE given a default value of zero, but I did NOT continue that process with my copper and silver ores. So, I can say that I did NOT actually give these ores any default metadata value myself. Was I supposed to? I was not shown this in the tutorial I read, nor was that ever mentioned as a point in the procedure of creating your own "custom" ore and ingot pairs...

 

   I think I am going to have to go back and see what other mods which create "custom" ores are doing, say, when they are "dropped" after having been MINED or SMELTED, because apparently I am missing something in my block and / or item handling...

 

   Thanks anyways, and cheers to you!

   ZTagre.