In an extremely similar manner you can apply patches. Take a look.

The file to patch is the clean ROM you want to patch. The UPS patch is any UPS patch—for testing purposes use the one you just made.

Where it says “create backup of the file”, this is in case you aren’t sure if the UPS patching will work. It will make a back-up that you can go back to if the patch screws up your ROM. Pretty useful.

Another safety check is the “If file is invalid”. If a patch is applied to a file that wasn’t the same file the patch was based off of—i.e. the clean ROM—then NUPS will take an action depending on what you have selected. It will either abort it and not patch it, ask if you want it patched, notify you that the files don’t match (meaning your ROM isn’t clean/unedited), or ignore it as a whole and patch anyway as if though nothing odd happened. Take your choice and hit “patch” to apply the patch.

Lastly, we have a brand new feature not seen in IPS patching: “Get patch data”. What you do here is browse for a UPS file and hit “Check” and NUPS will tell you the offset of any data that was changed and the length of bytes changed at that offset.

Like so, where the offset tells where and the length (misspelled as “lenghts”) tells how long. You might think “this is so pointless” or something like that, but it’s actually useful for more advanced hackers. It tells you what data was changed, and where—you can use this to track what data was changed in small fix patches or ASM patches. If by some chance you don’t want part of a patch’s data, you could use this to help you find out where the part you don’t want is, and revert it back to normal, or vice-versa if you only want a specific part. There are many other uses for this feature but they are rather specific so I won’t get into them, but this feature has definitely saved me in a few instances by helping me solve my own bugs/glitches. Thus I’d keep it in mind for the future.

And with that, you can now use all of NUPS features!

Chapter 69: jfp Patching

WARNING: This chapter will not be as detailed as the others/assume you know little to nothing. Rather, it assumes you are familiar with the basics of patching. If you are new to patching as a whole, I suggest learning IPS and UPS patching first.

First of all, JFP patching was invented by Hextator as a better patch format than UPS. It has its advantages but I can’t think of them all now—I’m pretty sure that it uses a better format for checksums, is more compatible with FEditor Adv, and allows you to save the patched file separately from the unpatched file.

Second of all, you need the latest version of Java for this to work, so get that installed if you don’t have it already (chances are if Xeld’s other programs are working, you have it). Then extract the files (you’ll need WinRAR or 7zip probably, the archive will probably be a .7z) and go into the “Java Implementation” folder. Double-click on the “Drive” batch file which will load up a command prompt and then ask you:

“Are you creating a patch instead of applying one?”

Hit “yes” to create a patch, where you select the original file, edited file, and the path for the .jfp patch, in that order. Hit “no” to apply a patch, where you select the JFP patch, a clean ROM, and a path to save the new patched ROM (it does not apply the patch to the original file, but saves it as a separate file).

…And that’s all I have to say about that. It’s relatively easy and not complex even if it doesn’t have the greatest GUI. At least now you can deal with JFP patches without freaking out, right?