Setup old MCP / FML

Shell scripts to automatically set up old versions of MCP and FML

Scripts:

• setupFML1.2.5.sh: downloads and sets up a FML 1.2.5 environment.
  Requirements: curl, unzip, dos2unix if not on Windows.
  Python 2 and Java are required for MCP setup (JDK 6 recommended, JDK 7 works as well).

Using specific JDK versions

On Linux or macOS, setting the version of Java used is generally very simple:

export JAVA_HOME=/path/to/java/home

On Windows, there's a few complications. Old MCP versions will check the registry key Software\JavaSoft\Java Development Kit for the value of CurrentVersion, and will use the JDK found under Software\JavaSoft\Java Development Kit\(value of CurrentVersion) if it exists. You may have to edit the registry to change this. If there's nothing in the registry, it will then use the version of java from javac in PATH, and searches various Program Files locations otherwise.

Old JDK downloads

Here's a table of older JDK download locations:

Java version	macOS	Windows	Linux
1.6, OpenJDK	SoyLatte	Azul Zulu	Azul Zulu
1.6, Oracle JDK	Apple Legacy JDK (32 bit)	Oracle Java 6 Archive	Oracle Java 6 Archive
1.7, OpenJDK	Azul Zulu	Azul Zulu	Azul Zulu
1.7, Oracle JDK	Oracle Java 7 Archive	Oracle Java 7 Archive	Oracle Java 7 Archive

Note for macOS users: it's generally easier to use Java 7 instead of Java 6 on macOS. The Apple Legacy JDK contains 32 bit components, and may not work on macOS 10.15+. I haven't managed to get SoyLatte working, but it's theoretically possible to use it.

Why?

Older versions of MCP and Forge take many steps to set up, and sometimes require fixes due to their age. I wrote a guide on how to install Forge 1.2.5 manually some years ago, which was fairly tedious. Using a shell script is hopefully easier than patching files manually.

License

All scripts are licensed under the BSD Zero Clause License.