Open OmerMor opened 8 years ago
This seems out of scope for SCI Companion. I feel this might be better done as an external tool, perhaps using the text files generated from the View Resource Map and View Message Map buttons in the Version Detection dialog.
Although I guess that might be pretty difficult...
To be honest, I can't even get MAKEVOLS to work, RESOURCE.TXT file or otherwise.
Given I don't really know the format for resource.txt (it seems to be fairly different for different SCI versions, from what I've seen), something fairly easy I could do is just have functionality that lists the resources in the package files in the form of
script 123 view 456
etc... then those who want to could cobble together a complete one fairly easily.
This is what I managed to use:
(someKeyword
; first entry is makevols' default choice if none given as argument
script 123
view 456
...
)
; more (blocks) can follow, and can reference eachother.
(cdrom
intro
rm1
...
system
)
(system
script 255
heap 255
view 999
...
)
Was there any success in using makevols to repackage resources?
In the last five years? Not on my part.
(requested by NewRisingSun in http://sciprogramming.com/community/index.php?topic=1420.msg10242#msg10242)
If I may request an additional feature: the ability to produce a
RESOURCE.TXT
file from an existing set of RESOURCE.* packages, so I can use it with Sierra'sMAKEVOLS
to repackage a changed game with compression. This could be implemented as an option in the "Extract all resources" window. I have, more or less manually, written aRESOURCE.TXT
file for SQ1 thatMAKEVOLS
will accept and yields identicalRESOURCE.*
files to the released game when fed with extracted unmodified resources.