Rebuilding resource.000 with external patches

[Charles]

Is there any easy way to rebuild a resource.000 with all the external patch files?

I thought Tools-->Rebuild resources did it, but it looks like that just removes duplicates from within the resource itself, not adding in any additional patch files.  I feel like I'm missing something obvious.

[troflip]

Is there a checkbox for "Manage resources as patch files" in Game properties?

Not sure if that was a private thing I added or not... or how well tested it was.

[Collector]

Is there a checkbox for "Manage resources as patch files" in Game properties?

Not sure if that was a private thing I added or not... or how well tested it was.

It's a checkbox in the Game Properties dialog.

[Charles]

Ah yes, I remember the discussion of that option a few years back -- I was kinda hoping there'd be a way without me substantially altering my workflow. Toggling the "Manage resources as patch files" has some pretty serious consequences that I wasn't looking to implement at this stage.

I'm using Kawa's build v3.2.3.0, btw.

Toggling it on has a fairly lengthy pause while it extracts each resource to an external patch file -- not sure if it overwrote any existing patch files with their (older) internal resource counterpart -- also not really sure if there were any overlapping files there... it's been nearly a year since I touched this mod.

Once all the patch files were extracted, the Explorer only showed patch files, not any files already existing in resource.000. But Tools-->Rebuild resources seems to have worked as I'd wanted.

Trouble is when I uncheck the "Manage resources as patch files" to change things back to how I had it before, it's asking me for confirmation after it deletes every single script file.  It also asks if I want to delete the corresponding script source code (thank goodness that's not checked by default).

I'm just going to hard-crash SCICompanion and restore from the zip I made beforehand -- I don't feel like clicking yes on 285 individual confirmation dialogs tonight. It'd be really nice if the Rebuild resources window itself could just build those patch files in without needing "Manage resources as patch" enabled.

[Kawa]

If the amount of patch files isn't too wild, I like to just import them, then rebuild to get rid of the older ones that just got replaced.

[Charles]

Ahah! Import patch file! I completely overlooked that. That's exactly what I was looking for. Thank you Kawa.

It's 185 or so I need to import, so not something I'd want to do often, but now that I know about the import option I can just import them as needed in the future.

[Collector]

Toggling it on has a fairly lengthy pause while it extracts each resource to an external patch file -- not sure if it overwrote any existing patch files with their (older) internal resource counterpart -- also not really sure if there were any overlapping files there... it's been nearly a year since I touched this mod.

I don't know for sure, but I would be very surprised if it didn't only extract ones specified by the MAP file and then only if there was no existing external patch.

[Kawa]

*seriously considers adding script support*

[Charles]

Honestly, I was tempted myself to attempt to modify the "Import patch file" menu item to allow selecting multiple files.  If multiple patches are selected, I'd skip the import dialog, and just use the default values.

Unfortunately I'm quite rusty in my C++, and don't want to take on another learning project. But if you do it, I'm very interested.

[Kawa]

Honestly, I was tempted myself to attempt to modify the "Import patch file" menu item to allow selecting multiple files.  If multiple patches are selected, I'd skip the import dialog, and just use the default values.

Unfortunately I'm quite rusty in my C++, and don't want to take on another learning project. But if you do it, I'm very interested.

So I took that as a personal challenge.

The actual release is in the link in my signature, as always.

[Charles]

Oh, this sparks joy.    Thank you, Kawa!

Looks like it's capping out at 25 views at a time.  I think it's related to this: https://stackoverflow.com/questions/14903496/why-cfiledialoggetnextpathname-doesnt-work-when-the-file-path-is-long.

Not really a problem. Just means I needed to import 5 times instead of 112 times.

[Kawa]

Ah yes. I actually had code similar to that in Barak Manos' answer at first but removed it since it seemed to Work Fine™ as-is. Might put it back, but it's almost three AM and I should've been in a more horizontal orientation since at least two hours ago.