[1.7.2] thoughts about manual deobfuscation

[libarclite]

Since eclipse is so powerful for refactoring, I'm tempted to manually deobfuscate methods as I discover what they do. However, I would like to provide a bread crumb for the reobfuscation process to use when I want to deploy my mod. Has anybody ever considered using Java annotations to leave such a breadcrumb? Something like:

 

@Retention(RetentionPolicy.RUNTIME)

@Target(ElementType.METHOD)

public @interface Breadcrumb

{

    /**

    * The unique mod identifier for this mod

    */

    String obfuscatedName();

}

 

Then when you rename a method, you'd write:

 

@Breadcrumb(obfuscatedName = "func_149711_c")

public Block setHardness(float hardness) { ... }

 

Thoughts?

[larsgerrits]

That could be very nice if forge would implement that!

[LexManos]

Not gunna happen, interesting idea, but the better solution that will happen, eventually, is that Forge will become independant of the mcp mappings allowing modders to contribuite to the central naming effort and see there work rewarded.

However, that requires some specialized tools to be re-written so will come in time.

[libarclite]

Well, I might look into implementing this myself. I've used BCEL for various other projects, so undoing my changes as a post-process might be doable. I would be interested to learn more about the new process, and would like to contribute.

[Chibill]

Find the names in the Mcp-srg files in the build/tmp dir somewhere.

[libarclite]

build/tmp/decompile/forge-1.7.2-10.12.0.993-srg.jar

build/tmp/reobf/reobf.srg

build/unpacked/conf/mcp-notch.srg

build/unpacked/conf/mcp-srg.srg

build/unpacked/conf/notch-mcp.srg

build/unpacked/conf/packaged.srg