Installing Minecraft Forge differs from other server jars such as bukkit because it requires downloading an installer jar, which downloads the actual executed jar (as well as the official Minecraft server jar).
Downloads for Minecraft Forge for Minecraft 1.16.4 Latest: 35.1.37 Recommended: 35.1.4. Downloads for Minecraft Forge for Minecraft 1.6.4 Latest: 188.8.131.525 Recommended: 184.108.40.2065.
This increase in procedural complexity can be handled relatively easy using the web-ui profiles, however. The steps outlined here have been tested to work for 1.7.x (1.6.x and previous require manual jar META-INF adjustments).
Downloads for Minecraft Forge for Minecraft 1.16.5 Latest: 36.2.19 Recommended: 36.2.0. Get a Minecraft server from ScalaCube - Minecraft Server Hosting. Install a Forge 220.127.116.115 (1.6.4) server through the Control Panel (Servers → Select your server → Game servers → Add Game Server → Forge 18.104.22.1685 (1.6.4)) Enjoy playing on the server! Posted July 14, 2015. On 7/14/2015 at 1:45 PM, diesieben07 said: 1.6.4 is no longer supported. Use 1.8 or at least 1.7.10 (or, IF you are using 1.6.4 for whatever dumb reason, the one you gave is not valid, use the.latest. version). Yes, I know that it is no longer supported.
Use the following template and change where versions and URLs differ:
<syntaxhighlight>profile name: forge172_installertype: standalone, runnable JARdownload url: http://files.minecraftforge.net/maven/net/minecraftforge/forge/1.7.2-10.12.0.1046/forge-1.7.2-10.12.0.1046-installer.jarsave download as: forge-1.7.2-10.12.0.1046-installer.jarjarfile to run: forge-1.7.2-10.12.0.1046-installer.jarjarfile arguments: --installServer</syntaxhighlight>
Update your profile so a checkbox appears in the profile listing.
Using the 'Create a new Server' tab, name and establish starting settings for your server. For profile, choose 'forge172_installer'.
Start the server. For a few moments (~20 seconds), your server will download the Forge libraries and the official Minecraft server jar. You can verify successful completion of this step by checking the files in your server's live directory (sample server name is a below):
<syntaxhighlight>[email protected] servers/a# lsforge-1.7.2-10.12.0.1046-installer.jar server.config [email protected] servers/a# lsforge-1.7.2-10.12.0.1046-installer.jar minecraft_server.1.7.2.jarforge-1.7.2-10.12.0.1046-universal.jar server.configlibraries server.properties</syntaxhighlight>
At this point, the server will go 'offline'; the installer jar isn't meant to be long-running. Next, looking at the file directory, two new server jars have downloaded, forge-1.7.2-10.12.0.1046-universal.jar and minecraft_server.1.7.2.jar. You will use the former to complete the next step. Note, that other Forge-based server suites may have different names such as cauldron-1.6.4-1.965.21.89-server.jar. You should be able to identify the jar intuitively by dismissing the official Minecraft server jar file as well as any jar with the word 'installer'.
Use the following details, ensuring that the 'jarfile to run' matches precisely the downloaded file referenced above.
<syntaxhighlight>profile name: forge172type: unmanagedjarfile to run: forge-1.7.2-10.12.0.1046-universal.jarjarfile arguments: </syntaxhighlight>
'Unmanaged' means 'do not download anything, simply run the jar file as entered.'
Change your server to use the new profile forge172. Now when you start the server, it should again indicate 'Server successfully started', and stay 'up'. Successful configuration can be verified by checking for log entries in the console.