Variable names none intuitive etc.

[evildoctorbluetooth]

Hey guys, after taking a break from modding for a while, I returned to the scene, and I am currently operating on forge version 3.3.7

 

Perhaps it is my inexperience, but I have become confused with the variable name changing.

I will give an example.

 

Within block flower, the name of a function reads:

public boolean canPlaceBlockAt(World par1World, int par2, int par3, int par4)

 

Now can anybody tell me why this is better than:

 

public boolean canPlaceBlockAt(World World, int x, int y, int z)

 

Code is hard enough to read as it is, without none intuitive names of variables.

[LexManos]

Welcome to the world of decompiled code.

[evildoctorbluetooth]

Welcome to the world of decompiled code.

 

Oh yeah, I agree, but isn't this what the deobfuscating is for?

[LexManos]

Go complain to the mcp team to enable the mapings of parameter names.

Its setup to allow it but the database backend isnt setup.

So ya... just got to live with it.