From MineOS
Jump to: navigation, search

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).

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).


Create the forge172_installer profile

Use the following template and change where versions and URLs differ:

profile name: forge172_installer
type: standalone, runnable JAR
download url:
save download as: forge-1.7.2-
jarfile to run: forge-1.7.2-
jarfile arguments: --installServer

Update your profile so a checkbox appears in the profile listing.

Create your server

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):

root@core servers/a# ls
forge-1.7.2-  server.config
root@core servers/a# ls
forge-1.7.2-  minecraft_server.1.7.2.jar
forge-1.7.2-  server.config

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- 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".

Create the forge172 profile

Use the following details, ensuring that the 'jarfile to run' matches precisely the downloaded file referenced above.

profile name: forge172
type: unmanaged
jarfile to run: forge-1.7.2-
jarfile arguments:

"Unmanaged" means "do not download anything, simply run the jar file as entered."

Start your server

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.

What the profiles look like when entering: