Skip to content

Instantly share code, notes, and snippets.

@pwn3r1

pwn3r1/Setting up MCP without a full MCP release.md

Forked from Pokechu22/Setting up MCP without a full MCP release.md
Created July 26, 2021 13:46
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save pwn3r1/17f1de6b735ceb33a8b7f1cbdcef24d7 to your computer and use it in GitHub Desktop.
Save pwn3r1/17f1de6b735ceb33a8b7f1cbdcef24d7 to your computer and use it in GitHub Desktop.
Download ZIP
Setting up MCP for newer versions (e.g. 1.12.2)
Raw
Setting up MCP without a full MCP release.md

It's possible to use create an MCP installation for versions of Minecraft where there hasn't been a full MCP release. It takes a little bit of manual setup, but the end result is highly useful.

  1. Download and extract the most recent MCP build from http://www.modcoderpack.com/. (Currently, the latest build is http://www.modcoderpack.com/files/mcp940.zip)

  2. Edit version.cfg in the conf folder, and change ClientVersion and ServerVersion to the version you want (for instance, 1.12.2).

  3. Download the SRG zip for the version you want; these can generally be found at http://mcpbot.bspk.rs/mcp/<version>/mcp-<version>-srg.zip (for example, http://mcpbot.bspk.rs/mcp/1.11.2/mcp-1.11.2-srg.zip) or at http://files.minecraftforge.net/maven/de/oceanlabs/mcp/mcp/<version>/mcp-<version>-srg.zip (for example, http://files.minecraftforge.net/maven/de/oceanlabs/mcp/mcp/1.12.2/mcp-1.12.2-srg.zip). (For 1.12.1 and 1.12.2, only the minecraftforge link works)

  4. Extract that zip into the MCP conf folder, overwriting files and the contents of the patches folder.

  5. Download the latest daily mappings from http://export.mcpbot.bspk.rs/. Even if they aren't for exactly the version you want, they will generally work.

  6. Extract the mapping zip into the MCP conf folder, overwriting files.

  7. Run MCP's decompile.bat as you normally would.

Note that for this to work, there must be a released SRG file for the version you want. The SRG file is what converts obfuscated names into an intermediate step where names are (mostly) the same between versions; the mappings files convert those intermediate names into the names you see and are used to.

Note that as always, the MCP license applies, even for development builds. Please read the LICENSE.txt included with MCP for more information about what you are and are not permitted to do.

An additional note: if you're using eclipse, you will need to manually fiddle with build paths due to updated libraries. You will also need to attach the native libraries, found in jars/versions/${VERSION}/${VERSION}-natives, to the libraries (e.g. LWJGL) for the game to launch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment