Tutorial/Guide on how to use this?

[GavinRay97]

Really useful tool -- thanks for writing it! However, it would be great if there was some documentation on how to use it.

I imagine the most common usecase is something like:

• Import .jar/directory of .jars from <original>
• Import .jar/directory of .jars from <modified>
• Display a pretty diff of the modified methods and classes

I've managed to figure out how to import two .jars but I'm not really sure how to view only the differences.

[Player3324]

It is not so much a diff tool (doesn't even have a proper diff view) but for finding common parts between obfuscated jars. Tools like Proguard assign random names to everything so a minor update may look completely different, Matcher tries to undo this so 3rd party work against the old jar can be ported to the new jar without starting over.

[GavinRay97]

Ah okay thank you -- that's slightly different from my specific usecase where the source code is 99% the same between the .jar's but there are a few .class-files with manual patches that I'm trying to understand.

Appreciate the response (and still think it'd be useful to have some general documentation/screenshot tutorials) 👍

[BaalNetbek]

From what I've figured out. A simplest usage would be something like this.

Basic Tutorial

You need:

• somewhat new java in path. If I got it right version >=17 requiered.
• two version of a java program and a mapping file for one of the .jars in one of supported formats (pic. 1) .

To start the Matcher run:

• ./gradlew run in bash
• gradlew.bat run in cmd (Windows)

In Matcher:

1. Load the files with File -> New project -> (Inputs A -> add, Inputs B -> add).
2. Load mapping for one of them File -> Load mappings.
3. Match classes Matching -> Auto match all.
4. Save new mapping File -> Save mappings.

Picture 1. Supported mapping formats.