Xcom wrote:Wait no I got it working
This is amazing. Thank you so much boshaw. I will try and finish that filter file and post it in here.
Some small details regarding the filter. Does the string of the name search for an exact match? By that I mean does "gfx/terobjs/ridges/grass/ee" need to be exactly the same for it to do edits?
If it does a contains() check it would work out much better in some instances. For example a simple "/tiles/" could edit all res names with the name containing "/tiles/" instead of finding each and every one and adding it to that list.
Edit: crap stoped working again
I dont seem to have a handle of how it works.
Edit 2 : I think the crashes were due to shortened filter paths. It seams its doesn't like when I give general res names. Have to be specific.
Right now the name of the file in the filter has to be exact and it's based on the res-folder itself.
So for example if you gave it "res/" then it would just append the name in the filter file onto "res/"
ie: if in the filter file you had "gfx/tiles/sometile" then it would look for the file "res/gfx/tiles/sometile"
I can work on changing it so it does how you say with the contains
The extension on the filter file doesn't matter either btw.
Also on another side note, you don't need to use LayerUtil anymore now that you have that. It can also extract haven resource files like LayerUtil did.
In order to use that to extract haven resource files do:
1) use the run-abcl.{bat,sh}
2) wait for "CL-USER>" to appear
3) type
- Code: Select all
(slu:run :mode :da :layers "layers/hnh" :args '("path-to-resource-folder" "path-to-wanted-extraction-folder"))
where "path-to-resource-folder" is the relative or absolute path to a folder with .res/.cache files
and "path-to-wanted-extraction-folder" is the relative/absolute path to the folder where you want the files extracted
that'll extract the files just like LayerUtil used to, i just haven't bothered to update my resource utility topic yet.