Hello! I’m having an issue: the texture of my animated block is not showing when using GeckoLib in a Forge 1.20.1 mod. I’m confident that the texture path is correct: assets/reignofnether/textures/block/vilka.png. The model was created in GeckoLib 5.0 (Blockbench), but the project uses GeckoLib 4.x, so I suspect the issue is incompatibility between the .geo.json format of GeckoLib 5.0 and the API of GeckoLib 4.x: layer/texture structure has changed, preventing the engine from finding the file. Could you please advise: 1) How to properly adapt a GeckoLib 5.0 model + texture to work in 4.x? 2) Should the texture path in getTextureResource include the .png extension? 3) What are the main structural differences in JSON between GeckoLib 5.0 and 4.x models? I can attach logs, folder structure, and the model upon request.

You hit the nail on the head GeckoLib 5.0 and 4.x use different geo JSON schemas, so using a v5 model directly in a 4.x environment will definitely break texture/layer mappings.

To answer your questions:

1. The easiest fix is to re-export the model from Blockbench specifically choosing the GeckoLib 4.0 format (or adjust the project setup in Blockbench settings before exporting).

2. Yes, getTextureResource requires the full ResourceLocation including .png (e.g., new ResourceLocation("reignofnether", "textures/block/vilka.png")).

3. The main difference is how bone hierarchies and texture UV mappings are structured inside the .geo.json file.

Try re-exporting as 4.x from Blockbench and it should fix the missing texture issue!