Skip to content

Commit

Permalink
Improve README formatting
Browse files Browse the repository at this point in the history
  • Loading branch information
@Marcono1234 @Hexeption
Marcono1234 authored and Hexeption committed Aug 18, 2021
1 parent 4d53ed4 commit 68da7f9
Showing 1 changed file with 31 additions and 31 deletions.
62 changes: 31 additions & 31 deletions README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -12,62 +12,62 @@

### How to use

- Import the build.gradle in Intellij.
1. 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.
2. Run the Gradle "setup" task in the mcp folder in IntelliJ - you may need to select View > Tool Windows > Gradle to get this option.

<img width="284" alt="373de4ebc77d5079584370dd7fbe8745" src="https://user-images.githubusercontent.com/4052647/46925924-71b7b680-d026-11e8-9c29-e3ed2e43f810.png">
<img width="284" alt="373de4ebc77d5079584370dd7fbe8745" src="https://user-images.githubusercontent.com/4052647/46925924-71b7b680-d026-11e8-9c29-e3ed2e43f810.png">

- 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.
This will generate the decompiled source code, which you can now find in the "src" folder in the project.

- 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.
3. Modify the source code as you please.

- 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
4. To test your modified code, go back to the Gradle tasks list (where you ran setup), and run the "runclient" task.
This will compile your new, modified game and run it, to allow you to test.

5. 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, and run the "build" task. This
will generate the new executable JAR file in the "build/libs/" directory.

<img width="266" alt="a647ab0eb336062ffd80c8e053e10266" src="https://user-images.githubusercontent.com/4052647/46925963-a297eb80-d026-11e8-8b02-cb621b559511.png">
<img width="266" alt="a647ab0eb336062ffd80c8e053e10266" src="https://user-images.githubusercontent.com/4052647/46925963-a297eb80-d026-11e8-8b02-cb621b559511.png">

- 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
6. 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
7. Go into that folder and delete the original Minecraft 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.
8. 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".
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.
9. 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 new name we've been using - 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
10. Using an archive manager (Ubuntu comes with one built in; Windows users can download 7-Zip), 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.

1. The folder "assets"
2. The folder "data"
3. The file "pack.png"
4. The file "pack.mcmeta"
1. The folder "assets"
2. The folder "data"
3. The file "pack.png"
4. The file "pack.mcmeta"

-Finally, still in that archive manager, delete the META-INF folder from your new JAR.
11. 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.
12. 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
the 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.

### How to add Optifine

[![](http://img.youtube.com/vi/ocz1tPI_YSE/0.jpg)](http://www.youtube.com/watch?v=ocz1tPI_YSE "How to add Optifine to MCP Reborn")
[![](https://img.youtube.com/vi/ocz1tPI_YSE/0.jpg)](https://www.youtube.com/watch?v=ocz1tPI_YSE "How to add Optifine to MCP Reborn")

### Creators:

Expand Down

0 comments on commit 68da7f9

Please sign in to comment.