Which modloader and version does my pack need?

It's listed on the pack's CurseForge or Modrinth page. If not, open the pack's `manifest.json`: the `id` under `modLoaders` is the loader and version, for example `forge-14.23.5.2854` or `fabric-0.15.11`.

Do I need to set the Server Jar File myself?

No. The Edition Installer sets it automatically when you install the modloader. You only set it by hand if you install a modloader manually.

Why does my server crash with `for invalid dist DEDICATED_SERVER`?

A client-side mod is in your `mods` folder. Find the mod named in the error, delete that jar, and repeat for any others.

My pack has no server files at all. Can I still host it?

Yes. Install the pack in a launcher to get its files, remove the client-only mods, then follow the four steps. Modrinth `.mrpack` packs can generate a server pack with a tool like Ferium.

How to Manually Install a Modpack | WinterNode Help Center

Manually install any Minecraft modpack by installing its modloader, setting the Java version, and uploading the pack’s files. Use this when your pack isn’t in the Modpack Manager, or it didn’t install cleanly.

The same four steps work for any pack and any modloader, no matter how the pack ships.

Install Your Modpack

Install the modloader. Use the Edition Installer to install your pack’s modloader (Forge, NeoForge, or Fabric) and Minecraft version. This also sets the boot jar for you, so the server starts on the right file.
Set the Java version. The panel does not set this for you. Match it to your pack’s Minecraft version, or the server crashes on startup. See Java Version Selection.
Upload your pack’s files. Upload the pack’s content folders (mods, config, and any others like scripts or kubejs) over SFTP. Do not upload a libraries folder or a loader jar. The Edition Installer already created those.
Start your server. It should show Online within 1 to 2 minutes.

Big pack? Upload a zip instead

A modpack’s mods folder can hold hundreds of files, which is slow and unreliable over SFTP. Zip the folders, upload the single zip, then right-click it and select Unarchive in the File Manager.

Not sure which modloader or version?

It’s listed on the pack’s CurseForge or Modrinth page. If you can’t find it, open the pack’s manifest.json in a text editor. The id value under modLoaders is the loader and version you need:

"minecraft": {
  "version": "1.20.1",
  "modLoaders": [
    { "id": "forge-47.3.0", "primary": true }
  ]
}

No Server Files? Build From the Client Pack

Some developers never release server files. Get them from the client pack instead:

Install the pack in a launcher like the CurseForge app, MultiMC, or PolyMC, then copy its files to a folder on your PC.
Remove the client-only mods. They crash a server. See Common Errors below for how to spot them.
Follow the four steps above: install the modloader, set Java, and upload your mods and config folders.

Common Errors

Most modpack crashes come from one of these. Check your server log for the message.

A Client-Side Mod Is Crashing the Server

Some mods only run on the player’s PC and crash a server. The log shows:

[main/FATAL] [ne.mi.fm.lo.RuntimeDistCleaner/DISTXFORM]: Attempted to load class
net/example/mod/mixin/SomeClientMixin for invalid dist DEDICATED_SERVER

The phrase for invalid dist DEDICATED_SERVER means a client-only mod is in your mods folder. Find the mod named in the class path, delete that jar, and repeat for any others. Players keep these mods on their own end.

A Mod Is Missing a Dependency

A mod needs another mod (a library) that isn’t installed. The log names it:

[Server thread/FATAL] [FML]: MissingModsException: Mod tconstruct (Tinkers' Construct) requires [mantle@[1.12-1.3.3.49,)]

Download the exact version listed and add it to your mods folder. If it’s already there, the version is wrong.

The Server Runs as Vanilla, or “Unable to access jarfile”

The boot jar is wrong. This usually means the modloader wasn’t installed, or a loader installer got uploaded instead of the server jar. Install the modloader with the Edition Installer, which sets the boot jar for you.

The Server Won’t Start With Obscure Errors

This is usually the wrong Java version. Older packs (Minecraft 1.12 to 1.16) often need Java 8. See Java Version Selection.

Pack Pinned to a Specific Build?

The Edition Installer carries every stable Forge and NeoForge build, so almost any pinned build is in the version list. Find the build in your pack’s manifest.json (above) and select that exact version when you install the modloader.

If the Edition Installer doesn’t list the build (rare), contact our support team and we’ll install it for you.

Still Not Working?

If none of the above resolves your issue, contact our support team with:

Your Server UUID
The name and version of the modpack you’re installing
The last 50 lines of your console output