Describe the bug
EMF doesn't properly support Optifine file paths in .jem files for the "texture" field. This means that setting the "texture" parameter to "texture": "./textures/blastling.png" or even "texture": "./blastling.png" causes the mod to load the model without a texture. It seems that EMF only loads textures when the "texture" parameter has no slashes and points to a texture in the same folder as the model, like "texture": "blastling.png".

This creates a compatibility issue, as Optifine loads textures located in the same folder as the model only when the "texture" parameter includes "./".

As a result:

• A model with "texture": "blastling.png" will never have a texture with Optifine.
• A model with "texture": "./blastling.png" will never have a texture with EMF.

Additionally, EMF doesn't support placing model textures in subfolders, whereas Optifine supports this feature.

List and link to broken resourcepacks
resourcepack.zip

Screenshots
With Optifine:
With EMF:

Versions

• Minecraft Version: 1.21
• EMF version: 2.2.5
• ETF version: 6.2.4

fixed for next update

seems i forgot to actually remove the ./ and ~/ when they were used, so it checks for minecraft:optifine/cem/./textures/blastling.png whoops

can you double check that

thats a direct confliction of the optifine spec for cem textures

assuming the texture is ofcourse next to the model

Oh, it seems that both blastling.png and ./blastling.png work in Optifine 1.21-pre9. My bad. There used to be a long-standing bug where textures without "./" wouldn’t load in Optifine, so I thought it was still an issue.

Anyway, thank you for the quick fix!

Fixed in the newest version.