quilt-mappings VS vineflower

Quilt Mappings. Quilt is a fork of Fabric made by many former-Fabric developers. Quilt Mappings are like Yarn, but without a cleanroom, and so may take inspiration from the Official Mappings. Its main purpose is to be like Yarn, but Mojmappier, or to be like Mojmap, but Yarnier - depending on who you ask.

Honestly the way I learned is just downloading the code (https://github.com/hube12/DecompilerMC or https://github.com/QuiltMC/quilt-mappings are probably the best ways right now) and poking around until I found what I was looking for.

this is kind of a silly point, but the quilt community is just nicer to be around than any of the other ones in my experience, which has real effects: e.g., you attract people really really good at decompiler tech and create quiltflower which is a decompiler so good Java professionals use it. inclusivity matters! the cutting edge happens on quilt

The only way is to reverse-engineer it. Use something like quiltflower or javap if you want to be extra sure, and have a look through the Java code

Firstly, we have to decompile the JAR, turning the bytecode back into Java. This is a very difficult job: a lot of work has been put into the tools to make this happen.

Alternatively, there's this new project that I haven't tried yet: https://github.com/QuiltMC/quiltflower

The decompiler they used to view that code is not very good, that output is garbled.

If you're going to take apart JVM bytecode, you're better off using Recafe or Quiltflower.

https://github.com/Col-E/Recaf

https://github.com/QuiltMC/quiltflower

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

runs nice with jbang https://github.com/QuiltMC/quiltflower/releases/download/1.8.1/quiltflower-1.8.1.jar