Toolchain/1.16

This page is under construction.

This page is incomplete, and needs more work. Feel free to edit and improve this page!

The Forge toolchain is designed to clean up, merge, deobfuscate, rename, patch and provide the Minecraft source code for the usage of modders, researchers, or just those curious about how the game works.

This serves as an explanation as to how the development environment sets up your code, and aims to help you troubleshoot in case something goes wrong.

Overall process

When setting up the environment for the first time, a gradle refresh triggers three things:

1. ForgeGradle downloads the MCPConfig zip for the file you're using, and triggers the SetupMCP task.
2. After that, it processes the jar - applies access transformers, MCPCleanup and others
3. Finally, it patches and finalises the code, ready for modder consumption.

Needed knowledge

Obfuscation

Obfuscation is the process of renaming all of the fields, methods, and classes of the compiled code into unreadable, machine-generated names (such as aaa, bC), and removing package structures (this makes everything package-local and makes the obfuscated code smaller somewhat. This is commonly used by companies to prevent external entities from easily decompiling their released binaries/executables and retrieving their source code/intellectual property, though it does have size advantages.

Additionally, due to the way the Local Variable Table (LVT) of Java bytecode is stored, every function-local variable name is turned to ☃ (that's right, a snowman) in the compiled files. This makes immediate recompilation of the game literally and physically impossible, as every Java compiler currently available requires that local variables have unique names.

Minecraft is a commercial game, which means the source code is unavailable to all except the developers of Mojang. To prevent piracy and the copying of their intellectual property, Mojang applies this obfuscation process to the game before they release it. They use a tool called ProGuard, which is both an optimizer and an obfuscator.

Problematic Naming

There are a few big problems with using these obfuscated names directly for modding.

1. It is incredibly difficult to create mods using these obfuscated names. It requires immense patience to reverse-engineer the meanings behind each and every name, and to keep relating those names to what was already reverse-engineered. Although, tools do exist to make this process easier, such as IntelliJ IDEA plugins that provide naming hints automatically.
2. Because the obfuscation process takes place after compilation (the obfuscator operates on the compiled classes), the obfuscated names are not handled by the compiler. Thus, obfuscated classes may contain member names that are invalid in the Java source language, but valid in compiled bytecode (like ☃ discussed earlier); this means that the decompiled source of the game is not immediately recompilable.
3. These obfuscated names are automatically generated by the obfuscator for each independent release. This means that the obfuscated names may change signficantly between any two versions, making it harder for mod developers to update mods between releases.

SRGification

Some background on what SRG is and how it works:

SRG stands for Searge's Retro Guard; RetroGuard being an early attempt to reverse the ProGuard obfuscation, and Searge being co-author of the Mod Coder Pack or MCP, who created this process. Each obfuscated class, method, and field is assigned a unique number by the backend, via a sequential counter. This unique number is called the SRG ID of that class/method/field (henceforth called member).

The SRG name of the member is then derived from its SRG ID, its type (function {given the prefix func_}, field {given the prefix field_}, or parameter {given the prefix p_, or p_i if this is the parameter of a constructor}), and (optionally) the obfuscated name of the object at the time it was given its SRG name. This inclusion of the SRG ID into the name guarantees that the SRG name for all members are unique, and is the reason the ID is generated.

The actual conversion of obf names to SRG names is done by a tool called SpecialSource. More information on how it works can be found on that page.

The Setup

The process can be broken up into 3 steps; MCPConfig, patch and provide. The MCPConfig step is, understandably, the biggest and most prone to failure. An explanation of MCPConfig itself, how it works, what it's for (but NOT how to use it) can be found here. For the purpose of this guide, you need only know that its' goal is to get the game decompiled, and into a state where it can immediately be recompiled. Due to certain flaws in the rest of the toolchain, this means it needs to fix and patch the source code before passing it onto Forge.

In this way, MCPConfig can be thought of the vanilla side of the setup. It does not modify the game.

The following steps are all executed in order of appearance.

Download and parsing MCPConfig

The first thing that ForgeGradle does upon initialising a first-time setup, is starting the SetupMCP task.

This task then seeks to download the MCPConfig.zip jar for the version you're setting up. Once it is acquired, it parses the steps contained within the config.json. It does this by interpreting the file with the following rules:

• Every key, except for libraries, is interpreted as the name of a step.
• Steps are executed in order.
• The version value is interpreted as a maven coordinate of a file to download.
• If there is a repo value, it is used instead of the maven repositories defined in the buildscript, to retrieve the version.
• The args array is parsed, and {values} like this are interpreted as inputs, which can be substituted accordingly.
• Once the step is all parsed in, it is executed:
  • java -jar <version> <args> <jvmArgs>

An example config.json can be found here.

It defines the steps:

• mcinjector
  • version: de.oceanlabs.mcp:mcinjector:3.8.0:fatjar
  • args: --in {input} --out {output} --log {log} --level=INFO --lvt=LVT --exc {exceptions} --acc {access} --ctr {constructors}
• fernflower
  • version: net.minecraftforge:forgeflower:1.5.478.16
  • args: -din=1 -rbr=1 -dgs=1 -asc=1 -rsy=1 -iec=1 -jvn=1 -isl=0 -iib=1 -log=TRACE -cfg {libraries} {input} {output}
  • jvmargs: -Xmx4G
• merge
  • version: net.minecraftforge:mergetool:1.1.1:fatjar
  • args: --client {client} --server {server} --ann {version} --output {output} --inject false"
• rename
  • version: net.md-5:SpecialSource:1.8.3:shaded
  • args: --in-jar {input} --out-jar {output} --srg-in {mappings}
  • repo: https://repo1.maven.org/maven2/

More information about each of these tools can be found at the link provided, as well as what each of these arguments do. A brief description is provided.

MCInjector

MCInjector is the tool we use to apply various fixes to the code, while it is still in bytecode form. That meaning, it works on compiled code, not sourcecode. It does this because it's easier to rename LVT entries (from the snowman) to readable names while you can search for every other code path that references that specific entry; ergo renaming all accesses at once. This is impossible in sourcecode, where every name is identical and string matching is impossible.

It:

• Removes synthetic parameters from constructors
  • In bytecode, inner classes have the outer class as their first constructor parameter, but Java source code does not.
• Handles adding annotations for parameters that have synthetic data
  • In bytecode, these Nonnull (or whatever) annotations are attached to the parameters, not to the function that contains them.
• Adds constructors for inner classes
  • These are removed by Proguard sometimes, as they are not required in the bytecode if the parent has a default constructor.
• Adds synthetic (invisible) constructors for classes without them

It also applies fixes for things like EXC;

• Renaming parameters inside constructors, such that subclasses retain the ID of their parent.
• Fixing access for select functions, where it is required for the proper recompilation.
• Applying proper typing to constructor parameters
• Applying proper external (LWJGL) exception data to functions and classes.

Note that it does NOT rename to SRG. LVT (Local Variables) are renamed to lvt_<index>_<version>

ForgeFlower

After the code has been cleaned up by MCInjector, to a state where it no longer conflicts with itself, it can be passed to the decompiler.

The decompiler used by ForgeGradle is a custom fork of Jetbrains' FernFlower, called ForgeFlower.

It simply searches the jar for files, converts the bytecode into a reasonable best-guess interpretation.

As you can see by the repository, a lot of work has gone into tuning it for Minecraft's needs, but it is still a far way from perfect. This is why the patches are needed.

If you look at the patches for 1.16.4, they are mostly incredibly simple changes. Adding generics, making types more strict.

This is all stuff that should be done by the decompiler, and PRs are always welcome at the ForgeFlower repository for changes and fixes that would reduce the amount of MCPConfig patches required to get the game to compile.

For now, it is a necessity.

Mergetool

The game is split into two distributions; server and client.

Because the server contains no rendering code, and the client contains none of the server-specific code (like the UI), this means there are differences between what can run on one side or the other.

To get around this, we have a tool called Mergetool, which can search for the differences between two files (down to the function level) and merge them into one large (referred to as joined) jar file.

It is a simple program, but it works.

SpecialSource

SpecialSource is where SRG starts to come into play. It serves the role of our deobfuscator, performing deobfuscation.

This process is done with the help of a deobfusation map, a file generated by the original obfuscator (in this case, ProGuard) that contains a map of the obfuscated names to original, non-obfuscated names. This is commonly used on debofuscating stack traces outputted by an obfuscated program, for debugging purposes.

We have three sets of deobfuscation maps available to us; the obf->SRG mappings distributed with the MCPConfig system, the Yarn intermediary system, or the offical mappings..

To rectify this problem, Forge has it's own process to create deobfuscation mappings for the game, using community-sourced human-readable names. This process is split into two separate parts: the SRG renaming, and the MCP mapping. During the SetupMCP task, only the SRG renaming is performed.

SpecialSource itself operates on the source jar, as can be gathered by the name, and takes in a .tsrg file, like that contained in the MCPConfig zip.

It first renames classes, straight into MCP names. Then, iterating the members of the class, it renames fields, methods, parameters and inner classes.

A recap from earlier:

• For classes -> c_###_ (but it is immediately changed without the c_ being written to disk)
• For functions/methods -> func_<ID>_<obf-name>
• For fields -> field_<ID>_<obf-name>
• For function/method parameters -> p_###_#_ for normal methods, p_i###_# for constructors; the second number is the index of the parameter.

For example, func_71410_x refers to a function with SRG ID 71410 and original obfuscated name of x.

At this point, combined with the MCInjector step from earlier, we have a completely SRGed-up source jar.

Patches

Once we have the source code ready to go, the final step in the setup is to apply patches. These are done trivially, using diffs and gitpatcher.

Clean-up

Because of the way Proguard (or whatever obfuscator) and ForgeFlower mangle the source code, we need to take some steps to clean it up before we can proceed.

Assorted cleanup fixes are performed by the MCPCleanup utility. These include:

• removing trailing whitespace at the end of lines
• removing extra newlines at the start and end of files
• removing extra newlines between every line of code (every set of concurrent newlines is replaced with a single)
• removing comments (// hello, /* hello */)
  • the purpose of this step is unclear - it seems to be a preventative measure to ensure that Java changes do not interfere with the patch alignment in the future. Comments from the decompiler are still sometimes present in the source code.
• removing imports from the package a class is in
• removing comments that include the phrase GL_[^*]+
• replacing magic constants with their code substitutions
• replacing Character.valueOf(<character>) with <character>
• replacing OpenGL integer constants with their code representation
• converting unicode character constants back into integer representation
• formatting the code with JAStyle

It also adjusts abstract functions in some way - after running the program on a jar, the parameters of a default abstract function get renamed, but it is unclear exactly what part of the source code does this.

The Forge Side

After the MCPConfig/SetupMCP tasks are finished, ForgeGradle will print MCP Environment Setup is complete and wait for the user input.

The next step is to run the gradlew setup task, which does what it implies: Applying the Forge system to the processed vanilla code.

First, it applies ATs. After that, patches. Finally, MCP/Crowdsourced mappings are applied.

All in all, compared to the MCPConfig setup, this is a string of extremely basic tasks - mostly just one-line commands.

Applying Access Transformers

Access Transformers are a way of changing the visibility and finality of classes and class members. A full explanation of how it works, what the specification is, and what exactly they're used for, can be found at that page.

They are applied by passing the AT Config (nowadays called accesstransformer.cfg) into SpecialSource:

• SpecialSource.jar --in-jar {input} --out-jar {output} --access-transformer {at.cfg}

The current AT cfg can be found here.

Applying Patches

The patches used for Forge itself are different from those used by MCPConfig, which means there are two separate patching stages performed.

As opposed to the minimal MCPConfig patching, with the goal to make the code recompileable, the Forge patching is done to apply the API and modloader to the code.

It does this in a very similar way, with the gitpatcher utility.

Applying Mappings

This step isn't strictly necessary, and it can be ommitted. However, working with exclusively SRG names is confusing for most people, so we have an extra step to apply human names to the SRG.

These renames can come from any source; as mentioned earlier, the MCP/Crowdsourced naming, the Yarn naming, or the Mojang Obf-map naming. ForgeGradle does not care, as long as there is a valid SRG->names map.

How ForgeGradle retrieves these mappings is covered in the appropriate article.

The process of renaming itself is a simple regex substitution, performed by ForgeGradle itself. This is made possible by the assured uniqueness of SRG names.

Post-processing

At this point, the files are ready to go. We have processed the Minecraft jar such that it can be recompiled, we have applied appropriate access transformers and the Forge patches, and optionally renamed every applicable SRG name to whatever chosen distribution of mappings.

There is not much left to do but package the code into a jar file, and place it into the gradle cache (so that this process does not occur every single time the project is opened). It calculates this name based on many factors, and this is covered in the naming article.

Some additional Infos

1. You will never see c_XXX_ for classes, because the class names are picked beforehand
   • this is still crowdsourced, but before a new version is ready for Forge, all classes are given an MCP name
   • this MCP name stays constant throughout the game version it was picked for; it can change between versions, but it usually wont for already-named classes (except for misspells, typos, and misnames)
2. If you look into the JAR, you won't see any packages for the obfuscated classes, but the deobfuscated classes do have the packages, this is because the same process that names the classes, also decides what package they belong to
3. parameters have special names
   • there are two types of parameter names: p_XXX_X_ and p_iXXX_X_
   • the one with the i means that it's a parameter for a constructor
   • the first set of numbers are the SRG ID of their parent method, and the second number denotes the index of the parameter
   • the index of the parameter is a bit more involved, but this will not be explained here
4. If you look into the source, you'll see that parameters for lambdas don't have mapped names
   • This is because of a complication in how the lambdas are compiled/decompiled; it's a more advanced topic which involves how the compiler compiles lambdas which we will not explain here.

See also

• Obfuscation