I'm working on adding Python-style string slicing to AssetCooker Command Variables, meaning you'll be able to do something like this: { File[0:3] } to get the first 3 letters of the file name (and concatenate it in the path of the output or something). github.com/jlaumon/Asse...

GitHub - jlaumon/AssetCooker: ...
GitHub - jlaumon/AssetCooker: Asset Cooker is a build system aimed at game assets, for custom engines. It's FAST! It leverages Windows' USN journals to robustly track which files change, and only cook what needs to be cooked.

Asset Cooker is a build system aimed at game assets, for custom engines. It's FAST! It leverages Windows' USN journals to robustly track which files change, and only cook what needs to be c...

GitHub
It also means that { Dir_NoTrailingSlash } could just be replaced by { Dir[:-1] } (though I will probably leave it for backwards compatibility and because it's clearer for anyone not knowing how slicing works)
@jeremy.laumon.name *2 months later*
"Oh, by the way I also added f-string, don't ask me how it binds the variables, it just works"
@Ronflaix @jeremy.laumon.name haha not likely, but I did implement the AssetCooker DepFile format which was mentioned in the doc since day one but was left as a todo for a year!