threadtear VS Javassist

If you're very paranoid, Threadtear does have some amount of protection against potential code execution when decompiling, although it hasn't been updated in a while and it's still always a risk (albeit one I never personally encountered). If you suspect that the file you want to decompile does have a way to execute code when decompiling it, you could try using a virtual machine for some added protection.

I used recaf for the plugin.yml, I used deobfuscator to remove the obfuscation, then I used threadtear for decompilation. I use threadtear pretty much always, but it's allatori deobfuscation is somewhat lacking which is why I used a separate program. Also it does not show resources in the jar, which is why I had to use recaf.

learn java then get https://github.com/GraxCode/threadtear read all files be weary if its obfuscated

ClassPool comes from Javaassist library. It gives convenient API to retrieve the line number of Java method.

This problem can be resolved by https://github.com/jboss-javassist/javassist/blob/master/src/main/javassist/util/proxy/DefineClassHelper.java perfectly, I will use some of its code to fix this problem on 0.0.1

Other higher-level abstractions like Javassist: are all based on ASM, but have a nicer and easier-to-understand APIs to deal with.

In the following snippet, the transformer uses Javassist: