Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Produce RESOURCE.TXT Files #9

Open
OmerMor opened this issue Oct 21, 2016 · 7 comments
Open

Feature Request: Produce RESOURCE.TXT Files #9

OmerMor opened this issue Oct 21, 2016 · 7 comments

Comments

@OmerMor
Copy link
Contributor

OmerMor commented Oct 21, 2016

(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's MAKEVOLS 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 a RESOURCE.TXT file for SQ1 that MAKEVOLS will accept and yields identical RESOURCE.* files to the released game when fed with extracted unmodified resources.

@icefallgames
Copy link
Owner

icefallgames commented Oct 25, 2016

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.

@icefallgames
Copy link
Owner

Although I guess that might be pretty difficult...

@Kawa-oneechan
Copy link

To be honest, I can't even get MAKEVOLS to work, RESOURCE.TXT file or otherwise.

@icefallgames
Copy link
Owner

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.

@Kawa-oneechan
Copy link

Kawa-oneechan commented Oct 29, 2016

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
  ...
)

@skadarnold
Copy link

Was there any success in using makevols to repackage resources?

@Kawa-oneechan
Copy link

In the last five years? Not on my part.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants