How to Install a Modpack on an AMP Minecraft Server

Running a modded Minecraft server through AMP (Application Management Panel) is a popular choice for server hosts who want a clean, browser-based interface to manage their instances. Installing a modpack on AMP isn't quite the same as dropping files into a standard server folder — the process involves a few specific steps that depend on your modpack source, your AMP version, and how your server instance is configured.

Here's what you need to know to get it working.

What Is AMP and Why Does It Handle Modpacks Differently?

AMP, developed by CubeCoders, is a self-hosted server management panel that runs Minecraft (and other game servers) inside isolated instances. Each instance is essentially its own sandboxed environment with its own Java version, memory allocation, and file structure.

Because of this isolation, you can't always rely on auto-installers the same way you might with a bare-metal server. Modpacks — which bundle together a mod loader (like Forge or Fabric), configuration files, and a collection of mods — need to be installed in a way that AMP's instance structure recognizes.

Before You Start: What You Need

Make sure you have the following ready before touching any settings:

• AMP installed and running with at least one Minecraft Java Edition instance created
• The server-side modpack files — most modpack platforms (CurseForge, Modrinth, ATLauncher, FTB) offer a dedicated server pack download, separate from the client version
• Sufficient RAM allocated to the instance — modpacks vary wildly, but most mid-sized packs need at least 4–6 GB assigned
• The correct Java version — Minecraft 1.16 and below typically runs on Java 8, while 1.17+ requires Java 16 or 17; AMP lets you set this per instance

⚙️ Using the wrong Java version is one of the most common reasons a modded server fails to start.

Step-by-Step: Installing a Modpack on AMP

1. Download the Server Pack

Go to the modpack's page on CurseForge, Modrinth, or the relevant launcher site. Look specifically for the "Server Files" or "Server Pack" download — not the client-side zip. These files are pre-configured for server use and typically include the mod loader installer or a pre-built server JAR.

2. Stop and Back Up Your AMP Instance

Before making any file changes, stop the instance from the AMP dashboard. If you have an existing world or configuration you want to keep, back up the instance directory first. AMP stores instance data in a path like:

/home/amp/.ampdata/instances/YourInstanceName/ 

The exact path varies by OS and install method, but the AMP dashboard's File Manager can also be used to navigate and download files directly.

3. Upload the Modpack Server Files

Using AMP's built-in File Manager or an SFTP client (like FileZilla), upload the contents of the server pack into your instance's root directory — typically the Minecraft subfolder within the instance path.

If the server pack includes an installer script (common with Forge packs), you'll need to run it. This is done via AMP's Console tab or through SSH:

java -jar forge-installer.jar --installServer 

This generates the necessary server JAR files that AMP will need to launch.

4. Update the Server JAR Path in AMP

After installation, the modpack will have created a new JAR file — for example, forge-1.20.1-47.x.x.jar or a run.sh launch script. You need to tell AMP to use this file.

In the AMP dashboard:

• Go to Instance Settings or Configuration
• Find the "Jar Filename" or "Startup Parameter" field
• Update it to point to the correct modded server JAR

Some Forge versions use a @libraries argument system. In those cases, you may need to reference the run.sh or run.bat script instead of a JAR directly, which requires adjusting AMP's startup command in the Application Settings.

5. Allocate Memory and Set Java Version 🧠

Back in the AMP instance settings:

• Set Java version to match what the modpack requires (check the pack's documentation)
• Increase maximum RAM to accommodate the modpack — heavier packs with 200+ mods often need 6–10 GB to run stably
• Optionally add JVM arguments for garbage collection tuning (common recommendations exist for modded servers, such as Aikar's flags)

6. Accept the EULA and Start the Server

Make sure eula.txt in the instance directory contains eula=true. AMP sometimes does this automatically, but with a fresh file upload it may reset. Then start the instance from the dashboard and watch the console output for errors.

Common Variables That Affect the Process

What Changes Between Simple and Complex Setups

For a lightweight Fabric pack with a small mod list, the process is relatively quick — upload files, point to the JAR, start the server. For a large Forge modpack with 150–300 mods, you're more likely to encounter startup crashes caused by mod conflicts, missing dependencies, or RAM limits being hit before the server fully loads.

Server packs from well-maintained modpack authors tend to include a server.properties, pre-configured config/ folder, and sometimes a startserver.sh script — all of which smooth out the process considerably. Community-assembled packs or those pulled from client-side installs often need more manual adjustment.

Your specific outcome depends on the modpack you've chosen, how your AMP instance is currently configured, and the resources available on the machine running it.