gstelmack
12-17-2013, 07:01 PM
Attached is a new version of ResourcePatcher. Note that this is no longer FOF specific, you can use it to patch any sort of executable you want. Also note that it can read BMPs directly, there is no need to create a resource DLL. So anyone who wants to push their mods out can just create a package and distribute it, and fans can then use this tool to apply them.
USAGE
The interface is straightforward. You have a button to set the path for any packages you want to consider applying. This path will be scanned for XML files, and assume those are package descriptors. Unless there are conflicts between bitmap file names, you can put as many packages in here as you want.
There is a button to set the target path. Use it to browse for the executable (in the case of most here, FOF7) you want to patch.
There is a "Make ORG" button. Use this to make a copy of the executable in its current directory with a .org extension. Do this once to keep a pristine version, if something goes wrong you'll want it to roll back.
There is a tree view on the left of all the packages you have installed, and all the individual patches included. This lets you pick and choose what parts of each package you want to install. You may want someone's bitmaps for part of the patch, and someone else's bitmaps for a different part.
Then there is the "Patch" button. This will apply all the patches you selected to the target executable. It will make a backup of the target exe with ".bak" as an extension. This gives you another level of backup.
USE THIS AT YOUR OWN RISK. I think this is safer than ResHacker, and easier to use, but you are messing around with executables. I will not listen to any complaining that it screwed something up. I can try and fix bugs, but if your FOF or any other install gets corrupted, well, I gave you two ways to back up your executable.
Creating Packages
I've also attached a sample package, TestPatch.zip. This is NOT for FOF, but an example. There are two BMP files and an XML. Unfortunately VBulletin doesn't seem to like me pasting XML in here, but you can open the file easily enough and follow along.
The "resources" line gives a name to your package that will be displayed at the highest level of the tree.
Each "entry" line is a single patch, and you can give it a name that also appears in the tree. An FOF example might be "Experience".
Each "substitution" line is a single resource replacement. The "tgtid" attribute is the number of the resource in the target executable you want to replace. The "pkgid" is the name of the BMP that should replace that resource image.
You can have multiple substitution lines for each entry line, as sometimes multiple bitmap resources need to be replaced together.
I'm not sure if we want to keep this thread for issues with Resource Patcher itself, or if anyone wants to add links to packages they create.
USAGE
The interface is straightforward. You have a button to set the path for any packages you want to consider applying. This path will be scanned for XML files, and assume those are package descriptors. Unless there are conflicts between bitmap file names, you can put as many packages in here as you want.
There is a button to set the target path. Use it to browse for the executable (in the case of most here, FOF7) you want to patch.
There is a "Make ORG" button. Use this to make a copy of the executable in its current directory with a .org extension. Do this once to keep a pristine version, if something goes wrong you'll want it to roll back.
There is a tree view on the left of all the packages you have installed, and all the individual patches included. This lets you pick and choose what parts of each package you want to install. You may want someone's bitmaps for part of the patch, and someone else's bitmaps for a different part.
Then there is the "Patch" button. This will apply all the patches you selected to the target executable. It will make a backup of the target exe with ".bak" as an extension. This gives you another level of backup.
USE THIS AT YOUR OWN RISK. I think this is safer than ResHacker, and easier to use, but you are messing around with executables. I will not listen to any complaining that it screwed something up. I can try and fix bugs, but if your FOF or any other install gets corrupted, well, I gave you two ways to back up your executable.
Creating Packages
I've also attached a sample package, TestPatch.zip. This is NOT for FOF, but an example. There are two BMP files and an XML. Unfortunately VBulletin doesn't seem to like me pasting XML in here, but you can open the file easily enough and follow along.
The "resources" line gives a name to your package that will be displayed at the highest level of the tree.
Each "entry" line is a single patch, and you can give it a name that also appears in the tree. An FOF example might be "Experience".
Each "substitution" line is a single resource replacement. The "tgtid" attribute is the number of the resource in the target executable you want to replace. The "pkgid" is the name of the BMP that should replace that resource image.
You can have multiple substitution lines for each entry line, as sometimes multiple bitmap resources need to be replaced together.
I'm not sure if we want to keep this thread for issues with Resource Patcher itself, or if anyone wants to add links to packages they create.