This is already in FFTactext, but it may also be useful for the other utilities.
This is relatively straightforward for FFTPatcher, as it knows what the original is.
Doing this for FFTorgASM may be more work:
I don't believe the suite knows what the original code looks like. It may require a diff with a known-good copy.
ASM patches are not changes, but groups of changes. How can one tell whether a change came from one patch or another? It may require going through all the patches and seeing if the binary looks like it had that patch applied, then checking for overlapping patches and selecting the bigger one, and finally listing unresolvable conflicts.
Combining the above notes: It is impossible to know whether a patch was applied if the patch consisted solely of variable changes (such as Xifanie's "X% chance of Critical Hit" hack), unless there's a known-good to diff against.
PS: I'm not sure how welcome such a change will be. People are scared of others copying their work.
PS: Glain, I am not asking you to implement this. I am just documenting.
Load a disk image to start editing it.
This is already in FFTactext, but it may also be useful for the other utilities.
This is relatively straightforward for FFTPatcher, as it knows what the original is.
Doing this for FFTorgASM may be more work:
PS: I'm not sure how welcome such a change will be. People are scared of others copying their work.
PS: Glain, I am not asking you to implement this. I am just documenting.