|Release Date||10 February 2015|
|Last Modified||01 November 2018|
Note: IPS Peek is no no longer under active development and has been open sourced (GPL V3): https://github.com/vector-man/IPS-Peek
IPS Peek is an IPS patch analysis tool.
Usually, IPS patch files can only be analyzed with hex editors; this can be difficult if the user has no knowledge of the IPS file format. IPS Peek allows IPS patch file data to be easily viewed in a visual way.
IPS patces can be opened, along with an optional target file (a file the patch is designed for). Each patch record can be clicked in a list, showing the data that is written to the file (in the Data View). Patch records can be selectively enabled or disabled for a given target file, and tested with an emulator, all from within the application. Patch report information can also be exported for later use.
- Selective patching with instant visual file diff.
- Emulator testing (with selected patch records).
- Supports loading of a target file to see how patch records affect it (with patched file diff and highlighting).
- Shows IPS patch records, record sizes, offsets and more!
- Shows Lunar IPS truncate extension (CHS).
- Shows data (in a hex view) written by a patch record.
- Shows total size of all modified data.
- Allows exporting of patch information to a text file for later use.
- Filtering support.
- Microsoft .NET Framework 4.0
Useful for version controlReviewed By: Miksy91 on 11 Oct 2018
I have been working on an extensive rom hack based on a binary rom file, and this tool has been exceptionally useful for validating, that I don’t accidentally cause unwanted changes (a.k.a “bugs”) to the rom file.
My hacking process is such that every time I start working on the hack, I have a backup of the hack at its current state. Once I have done some changes to the hack rom file, I’ll create an ips patch between the backup, and the hack at its current state. Next, I review the contents of that ips patch with this tool.
If the contents seem valid, and there are no unwanted changes, I “accept” the changes. This means that I archive the copy with a version, and create a new copy of the hack file as its current state. If there however are changes that I don’t recognize or seem invalid, I’ll check, what the data in those parts of the rom file used to be in the backup. If the contents in backup are correct, I fix them in the main hack rom file, and create another patch, and re-validate its contents.
Version 0.6.0 Recommended - Yes
|Useful for version control||Miksy91||11 Oct 2018||0.6.0||Yes|
|Great tool for organization||Corvo||14 Feb 2015||0.6.0||Yes|