[SUGGESTION] "Add support for subfolders and nesting"

[Ficusnt]

Please I'm begging you. Having a single folder with 400 variations named using numbers to have some sense of coherency is driving me insane. Make the .properties file be able to scan folders deeper than itself so skins.2=folder/subfolder/2 becomes a valid naming convention and all resourcepacks can be a lot more tidy and organized than they are.

No other mod does this, neither does OF.

An untapped QoL goldmine.

Thanks.

[SebSemos]

I would love Traben to expand in this direction or actually to shift from optifine for a more vanilla like system (like the items), But I guess it's too much work to support two systems.
In the meantime, my solution for more ogranised packs is to use the texture override in models. You can then have your textures in whatever folder you want, including your own namespace.
if you want more than one folder for the texture files, you just add several models with those different path.

[Ficusnt]

I would love Traben to expand in this direction or actually to shift from optifine for a more vanilla like system (like the items), But I guess it's too much work to support two systems. In the meantime, my solution for more ogranised packs is to use the texture override in models. You can then have your textures in whatever folder you want, including your own namespace. if you want more than one folder for the texture files, you just add several models with those different path.

Come again? I'm fairly new to this and while I managed to get by with surface level knowledge I think I really hit the wall hard with some limitations. What do you mean texture overrides in models? As in the "texture:" "path" field in the jem?

(My resource pack hit a completely different model-related and rule related wall rn with the fact that rules are consumed first match top to bottom, but I'd love to at least organize the old structure better)

[SebSemos]

Exaclty, in the .jem you can set the texture override, then in this folder you can have a .propertie (with the same name of your file)
If the propertie has no rule to match it will default the the file you put in the model.

Example here where I set the file in my own namespace folder
Folder path in the pack is assets\semos\textures\entities\humanoides\songs_of_war

[Ficusnt]

Oh I get it!
So I make a model per category I need, point them to where I need with that texture and inside I can make it iterate through random variations like usual? Or does it only work for a single texture? And then would I be able to put rules for which models get used in which circumstances using .properties alongside my models? Because that approach might just solve my issues.