minecraft source

[jonstar]

Hi!

 

Prior to gradle, mc source was in the project.  What I used to do was spend time renaming variables and things to make code easier to read and keep in my head.  Much easier when you know that p_70299_1 is a World object.  Is there any way to do something like that now? If there's a nicer way that others use to manage the source with saner names, I'm open to suggestions.

 

Thanks.

[Ernio]

I have no idea what you are talking about. I am almost certain you setup your workspace incorrectly:

Check this out: http://www.minecraftforge.net/forum/index.php/topic,14048.0.html#post_update_forge

 

Short: Download forge src and run setupDecompWorkspace then eclipse (or other)

[jonstar]

Ernio -- It's ok, I think you missed the whole 'prior to gradle' part of my post.  I'm just curious what is the best way to do what I used to do regarding mc source.  Right now I'm thinking to just extract the deobfuscated sources into another module/project and manage it that way -- nothing that would get compiled into the mod, just a place to keep source that I modify for saner names.

[jonstar]

That's pretty cool.  Thanks, I'm going to play with it.

[Guest]

In 1.8 parameter names can be named, and many of them are. I suggest you update.

 

Really? They named the parameters? If it wasn't so hard to update a mod to 1.8 I'd probably do that. I hate having to research what those weird parameters mean.

[jonstar]

So maybe the work days are too long... but I can't figure this out.  Are you saying that after moving to 1.8; I should be able to refactor -> rename parameters within a jar?  I did setup intellij for 1.8, ported a few basic mods over without issue but it still says,  "refactoring cannot be performed File.java is in a jar.".

 

All that I'm doing is cmd-clicking either an object or an inherited method that's taking me to the proper java source within forgeSrc*sources.jar.

[jonstar]

See.  I knew I was tired.  I read your "can be named" as I could name them.  Thanks again.