I am working on extending a mod that creates custom chemical compounds so that other mods could make their own custom compounds under their own namespace.  Drop a JSON in your data folder, call a few methods, fire and forget.

I want the calling mod's products to use the same textures as the core mod for ease of use and consistency.  I can't seem to successfully access the textures in the core mod from the calling mod.
I can force the model generation.  When I do, everything runs fine.  It's just that the items are completely invisible.  No magenta/black block, simply invisible.  That tells me that the model is there and being accessed, just no access to the textures that it references.
I want to avoid requiring that the consumer load a set of textures manually.
Here is an example of an item model that is generated.

{
  "parent": "minecraft:item/generated",
  "textures": {
    "layer0": "basemod:items/the_item_layer_0",
    "layer1": "basemod:items/the_item_layer_1"
  }
}

 

If this is 1.19.3, textures need to be in the item folder not items. See Mojang's change notes

Otherwise you are going to need to show more than just 4 lines of json, preferably on github.

Does changing it to use minecraft:item/apple work?

It's 1.19.2.  The textures are in the correct directory location in the called mod.
Yes.  Substituting "minecraft:item/apple" works for the calling mod.

Look at generateCompoundModels() on line 33 in ModItemModelGenerator.java.
The current location for the .texture is cleaned up.  I tried various configurations for the location.
One aspect that might that may be pertinent is that this is called by the calling mod from its datagen events as registered in addListeners() on line 104 in AddonRegisters.java.

It's not something I know a lot about, but I bet this has something to do with how you configure the existing files helper?

https://forge.gemwire.uk/wiki/Datageneration/States_and_Models

I am not configuring the ExistingFileHelper.  I am using the one from GatherDataEvent.
Are you suggesting that I make my own instance of ExistingFileHelper?

When I run it in debug, it shows that my test mod is the only existing pack and that forge is the only existing mod.

I have no idea what you need to do. I have never played with it. I only answered this question because of the 1.19.3 change.

The wiki says:

Quote

By default, only the vanilla datapack and resources are available to the ExistingFileHelper.

Of course, I might be completely misleading you into the wrong direction. As I said, I know little about this feature.

Edited December 30, 20222 yr by warjort