How does Mojang come up with obsfucation names like p_113322_322? It sure ain't done manually.

[Kiljaeden053]

Guess: Just like Minecraft world seeds, use any of letters and the returned numbers will be consistent. 

[Kiljaeden053]

Is that tool called proguard? Also is the obsfucation good enough that forge takes years to forward them.

[Draco18s]

5 hours ago, diesieben07 said:

Parameter names (like the one you quoted) are like local variables and as such they are all called ☃.

Yes, snowman.

Now I'm curious why.

3 hours ago, Kiljaeden053 said:

Also is the obsfucation good enough that forge takes years to forward them.

I don't think its taken "years" even for a major version. The longest delay I'm aware of was either 1.7 -> 1.10 or 1.12 -> 1.14

In both cases I don't believe it even took a full year. And I know for certain that the majority of the time waiting on 1.14 was due to a massive (absolutely massive) restructuring of Forge's own code to clean up and refactor huge sections of the core codebase to be more robust.

[Draco18s]

21 minutes ago, diesieben07 said:

And it doesn't matter what they are called, so someone chose the snowman.

Fair enough, was just wondering if there was a story there.

[Kiljaeden053]

Can I make my own SRG names for my mod and also use forge ones for obsfucation.

Edited August 13, 2020 by Kiljaeden053

[Kiljaeden053]

I want to obsfucate my mob codes so no more fighting. I have rivals accusing me of copying from them yet looking from their code they're the ones doing it and no one believes me.

 

I would obsfucate the code by using proguard and changing package names, I also want to use the forge SRG names to be even more confusing if that's possible, so that they can't guess that it's one of my mobs because it extends EntityLivingBase.