For display purposes only. I don't want to touch the actual code.

 

all I want is to get rid of the weird names (change the names of locals, parameters, fields and methods to something more meaningful); and maybe add a few comments. Is it possible? maybe there's some eclipse tool to do this.

Minecraft:

 

Short answer: No

Long answer: since the source code of Minecraft is not public (as I know), you need to decompile the minecraft.jar, do your stuff and recompile it back into an minecraft.jar

 

Forge: Yes, just set up your environment and import the source code and do your stuff. Afterwards you need to use your modified source code to create your mods but I guess this is more complicated than it sounds?

I don't know how to do that. When I open any class from ForgeSrc I can only read the source code, not edit it.

Yes because the source code is imported in the mod environment as library.

You need to open the source code itselfe as project, but I haven't looked into the project structure of the source code so maybe it's not that simple.

If I did that wouldn't that recompile Forge classes thus making my mods incompatible with other versions of Forge?

Maybe the build number changes but since you don't modidy the structure and signature of the classes it shouldn't be a problem.

 

One thing you can do:

 

search on google for "contribute to minecraft forge" or something, maybe there is a tutorial where you can see how the source code itselfe is set up in an IDE so you can modify the source code and build it and after this use the build jar as library in your mod environment.

I think the OP is asking for a more thorough debobfuscation (replacing srg names with meaningful names) as well as injecting comments along with hooks. These things are not done lightly, and they're not done "at home", but they are done by Forge's developers. Each major revision of Forge seems to name several more methods and variables for ease of reading. Comments are generally written on methods and fields injected by Forge, but Minecraft's vanilla elements are usually bereft.

 

To contribute your own advancement of Forge, you could start by locating the GIT repo and associated discussions. First learn the customs for suggestions and contributions so you don't stumble in and bother some very busy volunteers with headaches they've already dismissed. Once you've gained enough familiarity to speak up, then you might be able to offer up a useful suggestion. If you're especially ambitious, then you could study up on the scripting technology that decompiles Minecraft, injects Forge hooks etc. If you then write a generally useful "transform", you can learn how to submit what's called a "pull request" to offer your transform to Forge.

 

For the less ambitious: Whenever one of your mods encounters a srg name or poorly documented vanilla method, put your own comments into your own code. If you have some software methodology chops, you can organize your own modding in "layers", with your own interfaces, abstract classes etc to insulate your "on the ground" mod classes from the harsh pseudo-reality of decompiled Java.