Server Setup AMP

This page explains how to run GSPack on AMP (Application Management Panel by CubeCoders), on your own machine or with a host that uses AMP.

The idea: AMP installs NeoForge and manages Java and memory. You upload the GSPack files (mods, configs and scripts) that GSPackServerInstaller builds for you.

Not using a panel? The normal Server Setup is simpler.

What you need

• An AMP installation with the Minecraft module, and permission to create or configure an instance
• A PC with GSPackServerInstaller to build the server files
• At least 8 GB of RAM for the instance, plus some for the system

Step 1: Build the server files

On your PC, build the server in files-only mode. This downloads the server mods and configs but skips start scripts and Java, which AMP takes care of.

Windows:

powershell -ExecutionPolicy Bypass -File .\Build-ServerPack.ps1 -FilesOnly -AcceptEula

Linux / macOS:

./build-serverpack.sh --files-only --accept-eula

You now have a GSPackServer/ folder with mods/, config/, kubejs/ and the NeoForge installer jar.

Write down the NeoForge version. It's in the name of the installer jar (neoforge-<version>-installer.jar) in GSPackServer/. You need the exact same version in AMP.

Step 2: Create the instance

1. In AMP, go to Instances and click Create Instance.
2. Choose Minecraft Java Edition as the application, give it a name (for example GSPack) and create it.
3. Start the instance's management panel (Manage). Don't start the server yet.

Step 3: Set the server type to NeoForge

1. Open Configuration > Minecraft (in some AMP versions: Configuration > Server Type).
2. Set Server Type to NeoForge.
3. Set the Minecraft version to 26.1.2 and the NeoForge version to the version you wrote down in step 1.
4. Leave Server Jar on Autoselect. NeoForge doesn't use a classic server jar; AMP finds the right start files itself.
5. Click Update (on the Status page) so AMP downloads and installs NeoForge.

Important: the NeoForge version must match the pack exactly. If AMP picks a different (newer) version when you click Update, set the version again and update once more. Don't click Update later unless you mean to change the NeoForge version.

Step 4: Set Java and memory

Open Configuration > Java and Memory:

Setting	Value
Java version	The version Minecraft 26.1 needs (Java 25). Pick it from the list, or install it on the host first if it's missing.
Max heap size (memory)	8192 MB (8 GB). Use more if the host has it and many players join.
Additional Java options	Optional. You can leave this empty.

Don't upload user_jvm_args.txt or start scripts: AMP sets memory itself.

Step 5: Upload the GSPack files

1. Open File Manager in the instance. You'll see the server's root folder (with server.properties, libraries/ and so on).
2. Upload these folders from your GSPackServer/ folder into that root folder:
   • mods/
   • config/
   • kubejs/
   • any other folders from the build, such as defaultconfigs/
3. Don't upload the NeoForge installer jar: AMP already installed NeoForge in step 3.

Uploading many files: it's faster to zip the folders, upload the zip, and extract it in File Manager (right-click > Extract). Check afterwards that mods/ is directly in the root folder, not inside an extra subfolder like GSPackServer/mods/. If it is, move the folders up one level. You can also upload with SFTP: AMP has a built-in SFTP server, and the address and port are in the instance's configuration (or ask your host).

Step 6: Accept the EULA and start

1. AMP asks you to accept the Minecraft EULA on the first start (or set it under Configuration). Accepting means you agree to the Minecraft EULA.
2. Click Start on the Status page and watch the Console. The first start takes several minutes while all mods load and the world generates.
3. When the console shows Done, join with the server address and port shown in AMP (default 25565).

Make yourself operator by typing in the AMP console:

op <your name>

Updating to a new pack version

1. Stop the instance and make a backup (AMP's Backups tab, or download world/).
2. Build the new version on your PC with -FilesOnly (step 1) and note the NeoForge version.
3. If the NeoForge version changed, set it in Configuration > Minecraft and click Update.
4. In File Manager, delete the old mods/ folder first, then upload the new mods/, config/ and kubejs/. Deleting mods/ first prevents old and new versions of a mod from loading together.
5. Start the instance.

Your world, server.properties and whitelist aren't touched, and quest progress is kept.

Adding your own server mods

Put server-only mods (for example a backup or permissions mod) in the instance's mods/ folder through File Manager. Keep a copy, because you'll replace mods/ on every update. Or put them in extra-mods/ on your PC before building, so the installer adds them every time.

Troubleshooting

Problem	Fix
Server starts as vanilla (no mods load)	The Server Type isn't NeoForge, or mods/ is in a subfolder. Check step 3 and step 5.
Crash right after start with errors about the loader version	The NeoForge version in AMP doesn't match the pack. Set the exact version from step 1 and click Update.
"Unsupported class file version" or a Java error	Wrong Java version. Select Java 25 in Java and Memory.
Server runs out of memory	Raise the max heap size in Java and Memory.
"Channel … is missing on the server side" when joining	A mod was skipped as client-only but is needed on the server. Check skipped-client-mods.txt from the build, upload that jar to mods/, or build with -KeepClientMods.
A mod is missing	Check failed-mods.txt from the build and upload the missing jar yourself.
Upload is very slow or times out	Upload a zip and extract it, or use SFTP.

For general server questions (commands, claims, backups), see Server Setup. AMP-specific help: the CubeCoders community forum.