How to install a modpack on a Forge server

To run a modpack on Schokr, download the pack's server files, set your Forge server to the same Minecraft and Forge version the pack uses, and upload the pack's folders (mods, config and friends) with the file manager. There is no one-click modpack installer, but the manual process takes only a few minutes.

1. Check the pack's requirements#

On the pack's page (CurseForge or Modrinth), note:

• The Minecraft version, for example 1.20.1.
• The mod loader and version, for example Forge 47.x.
• The recommended memory. Large packs often want 6 GB or more.

If the pack uses NeoForge or Fabric instead of Forge, those are not among Schokr's listed templates. Ask in the Schokr Discord before going further.

2. Download the server pack#

Look for a "Server Pack" or "Server Files" download on the pack's files page. It is a zip containing folders like:

mods/
config/
defaultconfigs/
kubejs/
scripts/
server.properties
startserver.sh

The exact folders vary. Server packs leave out client-only mods, which is why you should not upload the regular client pack.

If no server pack exists, use the client pack's mods and config and remove client-only mods yourself. See client-side vs server-side mods.

3. Set up the Forge server#

1. Create a server from the Forge template, or reuse one.
2. In your server's Startup settings, set the Minecraft version and Forge version to match the pack, if the template exposes those variables.
3. Start the server once so Forge installs and creates its files, then stop it.
4. Give the server enough memory from your team's pool. On the free package your team has 6 GB in total, so a heavy pack may need most of it, or a store upgrade.

4. Upload the pack files#

1. Unzip the server pack on your computer.
2. In the file manager, delete the existing mods and config folders on the server if they only contain defaults.
3. Upload the pack's folders: mods, config, and any others it includes such as defaultconfigs, kubejs, scripts or resourcepacks. Uploading a zip and extracting it in the file manager is usually faster than many single files.
4. Skip the pack's start scripts (startserver.sh, run.bat) and installer jars. Schokr's Forge template starts the server for you.
5. If the pack includes server.properties, compare it with yours rather than overwriting blindly, so the server port stays correct.

5. Start and test#

1. Start the server. The first launch of a big pack can take several minutes.
2. Wait for the Done line in the console.
3. Players install the same pack version through their launcher (CurseForge app, Modrinth app, Prism Launcher and so on) and connect.

Common problems#

• Crash mentioning invalid dist DEDICATED_SERVER: a client-only mod is in mods. Remove it.
• "Missing or unsupported mandatory dependencies": the server's Forge version does not match the pack. See mod and version mismatch errors.
• Server stops without a clear error, or OutOfMemoryError: give it more memory. See memory and JVM flags.
• Players get "mod rejections" on join: their pack version differs from the server's.
• Disk full: big packs plus worlds can fill the 10 GB team disk. Delete old worlds, logs and crash reports.

Updating the pack#

Take a snapshot, then download the new server pack and replace mods and config (and other pack folders) completely. Leaving old mod jars behind causes duplicate mod errors.

Tip: for large uploads, you can also use an SFTP client like FileZilla. See how to connect with SFTP.