OK, I think I'm understanding how to use this.
It is not sufficient to just go down the list of patch modifications and enable them.
Some of them require additional mod work to make the patch function, correct?
OK, in the above example, the File: field is set to:
C:\Users\Steve\Downloads\SH5\TDW Generic Patcher\MODS\Objects_wind_direction_and_speed.zip
Now that file exists - it is part of what you get when you unzip the Patcher download.
But I assume that it is not sufficient to leave that zip file sitting there - I actually have to unzip that file (it's a mod) and use JSGME to install it?
In other words, the File: field is simply pointing me to the location of the mod archive. It's not the location where some file needs to be for the patch to run?
It would be cool if there was a front end you ran and you just chose which options you wanted and the appropriate patch was applied, plus any file manipulations were done for you.
It's kind of confusing to keep track of which patches need to be applied across which files (dependencies) and which files need to be manipulated outside of the patcher.
Steve