Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Proper deobfuscation mapping file format
See original GitHub issueAs far as I could see, you currently have two options for exporting user-made mappings (renames): the .jadx project file and .jobf mapping files. The issue is, .jadx contains much other information that’s not needed/wanted when I just want to get the mappings. And .jobf can neither handle Javadoc/comments nor is it easy to get them generated.
I suggest/request looking into adding .enigma or .tiny mapping format support, which are both currently used by FabricMC in their Minecraft deobfuscation toolchain. Enigma files look like this, for example: https://github.com/FabricMC/yarn/blob/1.19-pre2/mappings/net/minecraft/block/Block.mapping
It should be relatively easy to implement, too, via the mapping-io library. Maybe support for JADX’s mappings can be PR’d to there too, so conversion of legacy mapping formats would be possible?
Issue Analytics
- State:
- Created a year ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@NebelNidas more likely I will just remove
MTH_ARGvalue, because there is no easy way for me to get that info. And as I said, this is not really needed.Recaf also has some nice read-only implementations: https://github.com/Col-E/Recaf/tree/master/src/main/java/me/coley/recaf/mapping Mostly the same like mapping-io, but with more comments (and support for a few other mappings)