1.13->1.16.5
Swap to the 1.16-MOJO branch to view official mappings
-
Import the build.gradle in Intellij.
-
Run the setup in the mcp folder in intellij - you may need to select View > Tool Windows > Gradle to get this option.
-
This will generate the decompiled source code, which you can now find in the "src" folder in the project. Modify that source to change the code as you please.
-
To test your modified code, go back to the Gradle tasks list (where you ran setup), and run the "runclient". This will compile your new, modified game and run it, to allow you to test.
-
Once you have reached a final result you are happy with, there is a bit of a process to turn it into a JAR file that can actually run from the game launcher. Go to the "build" folder in the gradle tasks, an run the "build" task. This will generate the new executable JAR file in the "build/libs/" directory.
-
With that jar generated, open your Minecraft versions folder. On Linux, this defaults to ~/.minecraft/versions. On windows, it's in Appdata/Roaming/.minecraft/versions. Find the variant your modded version is based on (that is, if you modded 1.16.4, find the 1.16.4 folder). Duplicate that folder, and rename it. For me, I was modifying villagers so I called it "1.16.4_villager_mod".
-
Go into that folder and delete the original Minecraft's JAR file. Then, rename the JSON file to be identical to the folder name. For me, that made it "1.16.4_villager_mod.json".
-
Using a text editor, find the first instance of "downloads": . This tells Minecraft where to obtain the game JAR file. If you leave this in, Minecraft will automatically download the vanilla JAR. But we want to run your new modded JAR. So delete everything from that "downloads": through the client, server, and server_mappings headers, which finally end in
/server.txt"}},. Once you remove that, this section should hold"assets": "1.16", "complianceLevel": 1, "id": "1.16.4". The last thing we need to do in this JSON file is to change that ID field to match the name of the folder and the JSON file. So in this case, we want "id":" 1.16.4_villager_mod". -
Now, take your new JAR file from the build/libs/ directory, and copy it into this same version folder, and, for the final time, rename it to the name we've been using everything - 1.16.4_villager_mod.jar.
-
Using an archive manager (Ubuntu comes with one built in; Windows users can download 7zip), open the base version's JAR file (in this case, 1.16.4.jar, which you'll find in its folder), and your JAR file. You'll need to copy 4 files/folders from the base JAR into your new one.
- The folder "assets"
- The folder "data"
- The file "pack.png"
- The file "pack.mcmeta"
-Finally, still in that archive manager, delete the META-INF folder from your new JAR.
-Your files should all be configured now. In the Minecraft launcher (close and reopen it if it's already open), go to Installations in the upper left, and then create a new installation. Name it whatever you want. For the version, select your version you made (1.16.4_villager_mod.jar). Create it, then go back to the launcher home screen by clicking Play in the upper left. In the lower left, select your new custom version, and hit the big green Play button.
- Hexeption
- kingdevnl
- Cider