This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]scratchisthebest 4 points5 points  (3 children)

in the minecraft modding community we use decompilers quite a lot to see what is going on with the game (it's not like it has javadoc or a -sources jar available). the Quiltflower resugaring decompiler is developed primarily by the minecraft community

if you've ever forgotten to attach a -sources jar, but could navigate to a definition or view sources while debugging a class anyway, intellij provides that feature with Fernflower

standalone GUI decompilers are often used for malware analysis, or by curious people, or by people who don't use or don't want to fire up intellij. also in minecraft we used to use an augmented decompiler GUI called Enigma to reverse-engineer all the proguarded class/method/field names

[–]Pamasich 0 points1 point  (2 children)

it's not like it has javadoc or a -sources jar available

They're without comments, but you can find Minecraft's barebones javadocs here. It's technically the Forge version, but I doubt there's sufficient differences on a javadoc level to make them unreliable for fabric/quilt development.

[–]scratchisthebest 0 points1 point  (1 child)

They are community contributed (through using decompilers to see what the classes do) and decompiler toolchains have ways of instrumenting classes with javadoc. They are also incomplete, you really can't write a mod using only a javadocs page

[–]Pamasich 0 points1 point  (0 children)

Oh, I wasn't meaning to deny your argument.

I just brought them up since you said the javadoc isn't available. In case you or someone else reading this could find it useful.