How to add mods to workspace?

[LaughingJackalMC]

Hey, I was just exploring the workspace and found in the eclipse folder a 'mods' folder. What does this folder do? can you put other mods in it? Because that would be cool for testing integration!?                                           

[diesieben07]

Yes, you can put mods in it. They need to be provided in "deobfuscated" form though (that is with MCP names) or they will crash your game (unless you have CodeChickenCore, which can deobfuscate them at runtime).

[LaughingJackalMC]

Yes, you can put mods in it. They need to be provided in "deobfuscated" form though (that is with MCP names) or they will crash your game (unless you have CodeChickenCore, which can deobfuscate them at runtime).

 

is that just the jar form? sorry im a noob!

[jabelar]

is that just the jar form? sorry im a noob!

 

Obfuscation means that it isn't easy for human to read it.  So yes the JAR contains Java code but if it is obfuscated there won't be any nice comments or formatting, and all the field and method names will be changed to something that doesn't make obvious sense.  If you have a method called initializeMyBlock() when it is obfuscated it might be called m23438_b().

 

That is generally what obfuscation means.  Specifically for Minecraft modding the issue is that mods will call vanilla code and Minecraft vanilla code is normally obfuscated.  In Forge environment, thanks to the work of MCP, we can call vanilla methods with names that make sense (e.g. worldObj.isRemote), but in actual Minecraft it needs to call the obfuscated method (e.g. f2434356_b.f243435_b). 

 

So basically the mod will work in the Forge environment if it is calling the vanilla methods based on their deobfuscated names.

 

At least that is how I understand it.  I'm a noob too...

[diesieben07]

Mostly correct, but let me clarify some things.

With Minecraft, or rather Forge + MCP, there come basically 2 stages of obfuscation.

First of all there is the completely obfuscated form, as we get it from Mojang, which is just random letters used everywhere (methods named "a" or "xz", etc.).

These change every Minecraft version (even 1.6.2 => 1.6.4, at least most of the time).

 

Then there are the SRG names, which you cited (e.g. field_12345_a, func_12345_a). These stay mostly consistent between Minecraft versions, at least as far as possible.

If you reobfuscate your mod, it is transformed from the MCP names (which just translate the SRG names into a readable form) into these SRG names. Then at runtime FML deobfuscates the actual minecraft code (which contains method names like "a" or "x") into the SRG names, which is what allows mods to partially run cross-version (1.6.2 => 1.6.4).

[jabelar]

Thanks diesieben, I appreciate the time you take to write up these detailed clarifications.

[hohserg]

I'm sorry for necroposting... But how to add some obfuscated mod to 1.14+ workspace?

CodeChickenCore ceased releasing in 1.10 because Forge(or ForgeGradle or anything else) became able to work with obfucated mods out of the box. But it ceased work in 1.14.

Any ideas?

Edited September 8, 2020 by hohserg

[diesieben07]

20 minutes ago, hohserg said:

I'm sorry for necroposting... But how to add some obfuscated mod to 1.14+ workspace?

CodeChickenCore ceased releasing in 1.10 because Forge(or ForgeGradle or anything else) became able to work with obfucated mods out of the box. But it ceased work in 1.14.

Any ideas?

Look at the MDK build.gradle, it comes with an example for how to do it.